X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f Date: Fri, 01 Mar 2002 12:52:03 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: djgpp-workers AT delorie DOT com Message-Id: <2561-Fri01Mar2002125203+0200-eliz@is.elta.co.il> X-Mailer: emacs 21.2.50 (via feedmail 8 I) and Blat ver 1.8.9 In-reply-to: <3C7F3AFA.E44B5AFB@yahoo.com> (message from CBFalconer on Fri, 01 Mar 2002 03:25:30 -0500) Subject: Re: Malloc/free DJGPP code References: <10202281548 DOT AA27673 AT clio DOT rice DOT edu> <3C7E6500 DOT AFE5FEF7 AT yahoo DOT com> <3C7F3AFA DOT E44B5AFB AT yahoo DOT com> Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Date: Fri, 01 Mar 2002 03:25:30 -0500 > From: CBFalconer > > Not a sound from anyone on all this. Is this of total disinterest > to everybody? I did comment, about an hour ago; perhaps you still didn't see it due to propagation delays. In general, people here are quite busy. If you don't hear anything in a few more days, perhaps it could help asking more specific questions, if you have them. Eventually, the important question is "Since none of you objected, how about checking this code into the CVS?". ;-) > A further question - will raise(SIGSEGV) in the package on > detectable errors foul up the initialization sequence, since > malloc etc. appears to be called during it? I'd advise against raising SIGSEGV. Use SIGABRT instead: it has the same effect (abort with a traceback), but various parts of the library internals, in particularly dpmiexcp.c (which handles signals), know that it is not a ``real'' signal, so they treat it accordingly.