Mail Archives: djgpp/1998/04/13/12:22:38
Jonthan Van-Der Umms <sbmoore AT caribsurf DOT com> wrote:
> 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?
1) Yes gcc 2.8.0 have stabs debug information and it fixes a lot of debug
problems so if you or Sivakumar want better debug just use it. One problem of
gcc 2.8.0 for DJGPP is the broken C++ exception handling.
2) The Sivakumar problems looks like that: You have 2 files with the same name,
one located in the current directory and other not. The project makes reference
to the one not located in the current directory and when you debug the files
showed is the one in the current dir. It could explain this behavior.
SET
------------------------------------ 0 --------------------------------
Visit my home page: http://set-soft.home.ml.org/
or
http://www.geocities.com/SiliconValley/Vista/6552/
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
ICQ: 2951574
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(541) 759 0013
- Raw text -