dan@elroy.jpl.nasa.gov (Daniel Joseph Burns) (10/22/90)
Perhaps some of you Concurrent gurus can shed light on this problem of mine... I have a signal handler (SIGUSR2) that long jumps back to my main program. This works a fixed number of times, then it dies in sigvec. Should I be doing any special context cleanup before long jumping? I suspect that my problem is with the stack pointer. Any help is appreciated. -- Dan Burns dan@seti.jpl.nasa.gov Articles to: concurrent@soma.bcm.tmc.edu or uunet!soma.bcm.tmc.edu!concurrent Administrative stuff: concurrent-request@soma.bcm.tmc.edu Stan Barber, Moderator
bliss@sp64.csrd.uiuc.edu (Brian Bliss) (11/01/90)
If you're on a sun, and using setjmp/longjmp, as opposed to _setjmp/_longjmp, which don't save the signal mask, you shouldn't have any problems (at least I don't). are you using sigstack to define an alternate signal stack, and forgetting to set the ss_onstack field of the sigstack struct? bb Articles to: concurrent@soma.bcm.tmc.edu or uunet!soma.bcm.tmc.edu!concurrent Administrative stuff: concurrent-request@soma.bcm.tmc.edu Stan Barber, Moderator