From: DSB7 Newsgroups: comp.os.msdos.djgpp Subject: Re: rhide debugging -- possible bug? Date: Wed, 25 Mar 1998 16:00:40 +0000 Organization: University of Brighton Lines: 36 Message-ID: <35192A27.52A@bton.ac.uk> References: <3516FDE5 DOT 8EFD2C91 AT geocities DOT com> <35192AC2 DOT 54C9 AT plinet DOT com> NNTP-Posting-Host: itsuite180.it.bton.ac.uk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk 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 had exactly this problem, I eventually found it was because I wrote some code directly into a header file. It seems that Rhide didn't like treating them as containing code. Hope this helps, SeeYa, oooooooooo....... . . . . . . ( (--------------------------------------\ ( Dan Brown - D DOT S DOT Brown AT bton DOT ac DOT uk ) \--------------------------------------) ) . . . . . . .......oooooooooo