Arnaud Bergeron wrote:
"Use of this function by library threads that are not bound to
kernel-scheduled entities results in undefined behavior."
Note that it says library threads.
The distinction is lost on me. I thought threads are a kernel things
even if the API appears in another library.
How are you suppose to handle SIGSEGV when a thread blows its stack, if
you cannot set the alternate stack for the SIGSEGV handler in the first
place?
I don't what happens when a thread other than the main blows its
stack. But anyway, if you setup the alternate stack from the ain
thread you should have no problems. (It may be true for other threads
but I don't know.)
Hmm. I was under the impression that the alternate signal stack was per
process, not per thread, therefore you need only set it once in main()?
--
Anthony C Howe Skype: SirWumpus SnertSoft
+33 6 11 89 73 78 AIM: SirWumpus Sendmail Milter Solutions
http://www.snert.com/ ICQ: 7116561 http://www.snertsoft.com/
