From: pjfarley AT banet DOT net (Peter J. Farley III) Newsgroups: comp.os.msdos.djgpp Subject: Re: Are there any memory debuggers other than MSS and YAMD? Date: Thu, 21 Oct 1999 20:21:24 GMT Message-ID: <380f7243.297953@news3.banet.net> References: X-Newsreader: Forte Free Agent 1.1/32.230 NNTP-Posting-Host: 32.100.250.233 X-Trace: 21 Oct 1999 20:21:50 GMT, 32.100.250.233 Organization: Global Network Services - Remote Access Mail & News Services Lines: 35 X-Complaints-To: abuse AT prserv DOT net To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Eli Zaretskii wrote: >On Wed, 20 Oct 1999, Peter J. Farley III wrote: >> I'm running DJGPP v2.02, gcc 2.8.1 (10-28-98), libc/libg/libm 11-15-98 >> in a W95 DOS box, LFN=Y. >AFAIK, YAMD won't help you on Windows, since it uses several DPMI >functions for which you need CWSDPMI. Can you try this in plain DOS >mode? Sorry, I should have said I have already done so, with R4 of CWSDPMI, with no success in getting YAMD to actually report anything. I *did* RTFM, and Nate specifically states that YAMD must be used in plain DOS with CWSDPMI. My assumption at the moment is that I am not using it correctly, which is what I will be talking about privately to Nate. >> Call frame traceback EIPs: >> 0x00024b90 _malloc+192 > >Crashes at malloc+192 are a tell-tale sign of a program that either >overruns an malloc'ed buffer, or calls free more than once with the >same pointer. My deduction as well, without the benefit of knowing that this location in malloc is a symptom. >One possible approach to attack these problems goes like this: Thank you, Eli, I will try those instructions out and report the results later. ---------------------------------------------------- Peter J. Farley III (pjfarley AT nospam DOT dorsai DOT org OR pjfarley AT nospam DOT banet DOT net)