From:	Charles Terry <cterry AT plinet DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: rhide debugging -- possible bug?
Date:	Wed, 25 Mar 1998 08:03:14 -0800
Organization:	All USENET -- http://www.Supernews.com
Lines:	37
Message-ID:	<35192AC2.54C9@plinet.com>
References:	<3516FDE5 DOT 8EFD2C91 AT geocities DOT com>
NNTP-Posting-Host:	14229 AT 207 DOT 174 DOT 3 DOT 212
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Dan Chak wrote:
> 
> I'm using rhide v1.4.  I'm trying to debug some code that uses Allegro,
> and I've run into something very strange.
> 
> When I trace into a function (this seems to happen if the function is in
> another file, especially) instead of bringing the cursor to the
> appropriate line of the appropriate file, Rhide seems to choose an
> arbitrary line in the file to jump to.  Then if I keep pressing F7/F8 it
> moves the cursor down, but it has already started from the wrong place.
> 
> Anyway, this makes debugging impossible; I can't figure out where the
> program is actually crashing.  The reason I bring up Allegro is because
> I only noticed this started happening once I started using Allegro with
> my programs.
> 
> Is this a bug?  Or is there some way to fix this?  Please respond!  At
> the moment it's like I'm blindfolded looking for errors in my code.
> 
I don't know if its a bug- I'm not qualified to make
those kind of judgments but-
I've experienced three reasons for that happening that
are not bugs.
1) Not enough stack space in the program -read the docs to
deal with that.
2)  Stack is being overwritten by a bad pointer in the
program- my fixes for that are pretty esoteric :) but
I've heard there is a program called fortify to help with
that kind of stuff.
3) Sometimes with optimized code the actuall entry point isn't
even in the code anymore so the trace ends up at the end
of the function - but if you are crashing that probably isn't
the problem.
Isn't programming fun!!!

Good Luck
Charles Terry

- Raw text -