From: Nate Eldredge <neldredge AT hmc DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: upgrade chaos
Date: 13 Jan 2000 11:51:58 -0800
Organization: InterWorld Communications
Lines: 24
Message-ID: <83puv57ns1.fsf@mercury.st.hmc.edu>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1000112154156 DOT 258A-100000 AT is> <387D90EF DOT 1D5B0DCB AT mpx DOT com DOT au>
NNTP-Posting-Host: mercury.st.hmc.edu
X-Trace: nntp1.interworld.net 947793070 81302 134.173.45.219 (13 Jan 2000 19:51:10 GMT)
X-Complaints-To: usenet AT nntp1 DOT interworld DOT net
NNTP-Posting-Date: 13 Jan 2000 19:51:10 GMT
X-Newsreader: Gnus v5.7/Emacs 20.4
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

jazir <entropic AT mpx DOT com DOT au> writes:

> Yep I can do that.  Firstly I'd like to say that YAMD is a great program,
> as it helped me find memory leaks...but there were no msg'es about accessing
> memory not belonging to my program.  Once I had the leaks sorted, the only
> output was for successful allocation and deallocation of blocks.

Are you running in plain DOS, and using CWSDPMI as your DPMI server?
If not, that could be your problem; YAMD requires some special DPMI
services that Windows doesn't provide.

> In fact, when I compiled my program with YAMD, everything worked as expected.
> There was no crash..that could just mean that my bug goes back to doing no
> damage, as in djgpp v2.02, but YAMD should still detect it... i'm puzzled.

This is just what I'd expect if you're using Windows.  YAMD allocates
an entire page (4K) after your block.  Normally this is protected, so
an access will cause a fault, but if it is not (as on Windows), your
program will have another 4K to smash harmlessly.

-- 

Nate Eldredge
neldredge AT hmc DOT edu