Subj : Re: pthread_mutex_lock throws an exception on receiving signal 15
To   : comp.programming.threads
From : Casper H.S. Dik
Date : Wed Oct 05 2005 11:59 am

Paul Pluzhnikov <ppluzhnikov-nsp@charter.net> writes:

>"pankaj-startup" <pankaj.takawale@gmail.com> writes:

>> I was under impression that "undefined behaviour" means call to
>> particular unsafe function fails (in this case pthread_create)

>Your impression is incorrect. I told you this before, but you
>weren't paying attention :(  I'll repeat:

>  the result of calling any of them (async-signal unsafe functions)
>  in async-signal context is undefined: your program may appear to
>  work, or it may crash, or hang, or it may melt your CPU.

You forget the most interesting bit:

	... but usually only breaks after the code finds itself
	    in a shipping product.

You were lucky to hit the problem during development ....

Casper
-- 
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

.