Message-ID: <3EA53E2F.263C7FE6@yahoo.com> Date: Tue, 22 Apr 2003 09:05:51 -0400 From: CBFalconer Organization: Ched Research X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: djgpp-workers AT delorie DOT com Subject: Re: nmalloc revisited References: <10304211406 DOT AA25239 AT clio DOT rice DOT edu> <3EA41578 DOT 9E69308C AT yahoo DOT com> <4098-Tue22Apr2003105330+0300-eliz AT elta DOT co DOT il> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com Eli Zaretskii wrote: > ... snip ... > > I don't have access to a Unix box from where I type this: could > someone please look on Linux or SunOS/Solaris and see if they have > simple numbers, like 0, 1, 2, 3, etc. for malloc debug levels? > > > DBGKIND malloc_debug(DBGKIND level); > > This should be compatible to libmalloc.a on Unix systems, so again, > please someone look at man pages on such a system and tell what is > the prototype of malloc_debug, if there is any. Don't bother. I am going to put it back to the compatible version, and add a separate routine to set the dump file. As far as hooks go, the present .txh file says they are all DJGPP specific, and they don't exist in the libc documentation for 2.03, so I claim their implementation is up for grabs, and safety should be paramount. I will have to hook them to implement the automatic verification levels 2 up, which is why there needs to be an interlock. -- Chuck F (cbfalconer AT yahoo DOT com) (cbfalconer AT worldnet DOT att DOT net) Available for consulting/temporary embedded and systems. USE worldnet address!