From owner-freebsd-hackers  Fri Sep 19 13:58:43 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id NAA07826
          for hackers-outgoing; Fri, 19 Sep 1997 13:58:43 -0700 (PDT)
Received: from bcarsde4.localhost (mailgate.nortel.ca [192.58.194.74])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA07792;
          Fri, 19 Sep 1997 13:58:32 -0700 (PDT)
Message-Id: <199709192058.NAA07792@hub.freebsd.org>
Received: from bcars520.ott.bnr.ca (actually 47.128.5.188) 
          by bcarsde4.localhost; Fri, 19 Sep 1997 16:57:18 -0400
Received: from bnr.ca by bcars520.bnr.ca id <12675-0@bcars520.bnr.ca>;
          Fri, 19 Sep 1997 16:56:30 -0400
Date: 19 Sep 1997 16:56 EDT
To: nsmart@iona.com
Cc: tlambert@primenet.com, Don.Lewis@tsc.tdk.com, hackers@FreeBSD.ORG,
        freebsd-bugs@FreeBSD.ORG
From: "Andrew Atrens" <atrens@nortel.ca>
Subject: Re: Bug in malloc/free
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

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)
> 
>