I haven't dusted off my K&R to see what they have to say about
. I'm not completely sure what you mean by running in a different context. Very specifically, a signal handler does not share the same stack as the
One thing I started thinking about is what situations might result in signals being sent to my program during execution. The big one that comes to mind is stepping into someone else's memory space. I guess I could try to come up with a strategy that checked for a signal as part of the execution of certain types of calls. But that sounds like a lot of overhead. I'm a bit rusty on C++, but you can set up an exception handler to catch
On Sun, 12 Sep 2004 18:03:56 -0400
"Steven T. Hatton"