Xref: news-dnh.mv.net comp.os.msdos.djgpp:3528
Path: news-dnh.mv.net!mv!news.sprintlink.net!news.Edu.TW!newsserver.jvnc.net!news.caren.net!news.join.ad.jp!news.imnet.ad.jp!usenet.seri.re.kr!news.kreonet.re.kr!news.dacom.co.kr!newsfeed.internetmci.com!EU.net!Germany.EU.net!news.maz.net!cls.net!news
From: wiljo AT cls DOT de (Wiljo Heinen)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Bug hiding when using debugger.
Date: Thu, 30 Nov 1995 07:46:41 GMT
Organization: commercial link systems
Lines: 21
References: <49hcn7$elh AT news DOT manawatu DOT gen DOT nz>
Nntp-Posting-Host: wopr.cls.de
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:

>	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.
>	_ANY_ ideas on this would be greatly appreciated as I am getting
>rather tired of chasing a seemingly nonexistant bug.

Assuming the program's compile options where the same (i.e. also using
a -g compiled/linked version when not using a debugger) it could be a
timing problem. If you are using interrupt driven routines for
instance my bet would be a race condition. 

Regards

	Wiljo