* Dan Eischen <[EMAIL PROTECTED]> [011204 06:26] wrote: > > There are already cancellation tests when resuming threads > whose contexts are not saved as a result of a signal interrupt > (ctxtype != CTX_UC). You shouldn't test for cancellation when > ctxtype == CTX_UC because you are running on the scheduler > stack, not the threads stack.
That makes sense, but why? > You also have a bug in the > way you changed the check for cancellation flags. What? > There only clean way to fix this is to add a return frame > to the interrupted context so that it can check for cancellation > (and other things) before returning to the threads interrupted > context. No way to work around this? Shouldn't the thread exit library know which stack exactly to clean up even in the context of a signal handler? -- -Alfred Perlstein [[EMAIL PROTECTED]] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message