Date: 19 Sep 1997 16:56 EDT From: "Andrew Atrens" <atrens@nortel.ca> To: nsmart@iona.com Cc: tlambert@primenet.com, Don.Lewis@tsc.tdk.com, hackers@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re: Bug in malloc/free Message-ID: <199709192058.NAA07792@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
In message "Bug in malloc/free", nsmart@iona.com writes: > On Fri, 19 Sep 1997, Terry Lambert wrote: > > > > } We claim to be sort of POSIX conformant. Perhaps this is enough. We > > > } aren't actually POSIX conformant. All the above "safe" routines may > > > } clobber the global `errno'. > > > > > > Which is why I save and restore errno in signal handlers. > > > > Perhaps this should be done by the trampoline code on the user's > > behalf... > > Perhaps that would encourage people to write non-portable code. Detecting changes in errno ( when there should be no change ), would be useful for debugging. Armed with this knowledge the trampoline code could `SIGCORE' the offending app, or allow it to run, I guess it depends on your religion - I for one vote for SIGCORE. In either case I think it would be nice for the trampoline code to `repair' errno. Its the robust thing to do. Andrew. > > -- > Niall Smart > Customer Engineering, > IONA Technologies. (www.iona.com) > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709192058.NAA07792>