Date: Fri, 19 Sep 1997 07:15:18 -0700 From: John-Mark Gurney <gurney_j@efn.org> To: freebsd-bugs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Bug in malloc/free Message-ID: <19970919071518.15473@hydrogen.nike.efn.org> In-Reply-To: <199709191221.OAA10145@ws6423.gud.siemens.at>; from marino.ladavac@siemens.at on Fri, Sep 19, 1997 at 02:21:47PM %2B0200 References: <199709191221.OAA10145@ws6423.gud.siemens.at>
next in thread | previous in thread | raw e-mail | index | archive | help
marino.ladavac@siemens.at scribbled this message on Sep 19: > > > > > >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);? what happens what it's masked or caught?? Only SIGKILL and SIGSTOP can't be caught or ignored... (see signal(3) for more info)... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970919071518.15473>