From: Jonthan Van-Der Umms <sbmoore AT caribsurf DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: RHIDE Debugger - Problems
Date: Mon, 13 Apr 1998 00:59:15 -0300
Organization: Moore Paragon (Caribbean) Limited
Lines: 28
Message-ID: <35318D93.23AE@caribsurf.com>
References: <6gq17p$dds AT news DOT or DOT intel DOT com>
Reply-To: sbmoore AT caribsurf DOT com
NNTP-Posting-Host: pluto.edu.bb
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

Sivakumar Radhakrishnan wrote:
> 
> Hello Netters,
>                 I have been using the RHIDE debugger v 1.4 for sometime
> and have noticed an annoying problem. The Trace function (F7 or F8)
> does NOT work correctly. The lines seem to be out of place when
> execution proceeds to one of the many C files in my directory.
> I had used the -g option when compiling all the files.
> 
>         Could some RHIDE guru point out how this problem can
> be worked around.
> 
> Thanks
> 
> Siva
> 
> rsiva AT ichips DOT intel DOT com

I am aware that this is a problem with the debugging information.
something to do with "stabs" and "coff" debugging format. this was a
problem with the gcc2.7.2.1 port. there was a patch available on SET's
home page ans other sources. My question is has the problem been
addressed and fixed in the gcc2.8.0 port now available?

thanks,

nigel