Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!bcm!soma!concurrent-request
From: dan@elroy.jpl.nasa.gov (Daniel Joseph Burns)
Newsgroups: comp.sys.concurrent
Subject: Long jumps out of signal handlers
Keywords: sigvec, longjmp, setjmp
Message-ID: <2295@gazette.bcm.tmc.edu>
Date: 21 Oct 90 19:44:46 GMT
Sender: usenet@bcm.tmc.edu
Distribution: usa
Organization: Jet Propulsion Laboratory (NASA), Pasadena, California.
Lines: 14
Approved: concurrent@soma.neusc.bcm.tmc.edu
Nntp-Posting-Host: cortex.neusc.bcm.tmc.edu
Nntp-Posting-Host: seti.jpl.nasa.gov

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