Date: Fri, 19 Sep 1997 14:21:47 +0200 From: lada@ws6303.gud.siemens.at (marino.ladavac@siemens.at) To: bde@zeta.org.au, phk@critter.freebsd.dk Cc: mike@smith.net.au, atrens@nortel.ca, freebsd-bugs@FreeBSD.ORG, gram@cdsec.com, hackers@FreeBSD.ORG, julian@whistle.com Subject: Re: Bug in malloc/free Message-ID: <199709191221.OAA10145@ws6423.gud.siemens.at>
next in thread | raw e-mail | index | archive | help
> > > >Flushing in abort() should be safe because abort() is not among the > >functions that are safe to call from a signal handler :-). > > Bummer. > > So what should I do in malloc when I realize that continuing doesn't > make sense ? > > kill (diesig, getpid()); ? > for which value of diesig ? raise( SIGABRT );? or the equivalent kill( getpid(), SIGABRT);? /Marino > > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709191221.OAA10145>