Xref: news-dnh.mv.net comp.os.msdos.djgpp:3564
Path: news-dnh.mv.net!mv!news.sprintlink.net!tank.news.pipex.net!pipex!news.mathworks.com!newsfeed.internetmci.com!news.dacom.co.kr!news.kreonet.re.kr!usenet.kornet.nm.kr!ames!waikato!manawatu.planet.co.nz!news
From: terry AT manawatu DOT gen DOT nz (Terry Rozmus)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Bug hiding when using debugger.
Date: Sat, 02 Dec 1995 01:18:20 GMT
Organization: PlaNet (NZ) Manawatu, Palmerston Nth, New Zealand +64 6 357-9245
Lines: 26
References: <49hcn7$elh AT news DOT manawatu DOT gen DOT nz>
Reply-To: terry AT manawatu DOT gen DOT nz
Nntp-Posting-Host: privateer.manawatu.gen.nz
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

terry AT manawatu DOT gen DOT nz (Terry Rozmus) wrote:

>Hi,
>	I have been spending the last several days chasing an annoying bug
>that only appears when I don't use a debugger (any of them). I would
>be interested in knowing any differences for a program running under a
>debugger, and on it's own. The bug is that some dynamically allocated
>memory gets overwritten with other information whose source I cannot
>exactly track down.

	As often happens when I get to the point of asking for help, I solved
the problem the next day. A routine was expecting never to recieve
arguments outside a certain range (the only routine that I hadn't set
up checking on), and because of a bug it was getting them, this was
causeing a write outside a malloced block... 
	Thanks for the reply's. I think I'll be using more asserts from now
on!

Thanks
Malcolm


--
Terry Rozmus
terry AT manawatu DOT gen DOT nz