X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-bounces using -f
From:	"Matthew Smith" <matt AT the-good-stuff DOT freeserve DOT co DOT uk>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Debugging in RHIDE (1.4.9)
Date:	Tue, 5 Feb 2002 13:08:04 -0000
Lines:	30
Message-ID:	<a3olcf$iqs$1@newsg1.svr.pol.co.uk>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1020205122131 DOT 22332A-100000 AT is>
NNTP-Posting-Host:	modem-534.tiger.dialup.pol.co.uk
X-Trace:	newsg1.svr.pol.co.uk 1012914383 19292 62.136.210.22 (5 Feb 2002 13:06:23 GMT)
NNTP-Posting-Date:	5 Feb 2002 13:06:23 GMT
X-Complaints-To:	abuse AT theplanet DOT net
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4522.1200
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

> > Not until gcc is fixed to produce the right line numbers.  Ideally
> > RHIDE/gdb could be
> > adjusted to step to lines with no generated code too, by taking
the
> > next line which does have code.
>
> That would cause terrible mistakes in many cases, especially close
to end
> of one function and beginning of another.
>
Hmm. Maybe if RHIDE did a bit of compiling itself, to delineate the
functions, this would prevent problems.  It could then also summarise
the functions in each source file, which is a feature I would like.
Am I right in thinking that if the frame pointer is in EBP then it is
possible for a debugger to know the address of the function?

> The compiler should generate the correct info, and the debugger
should
> interpret it correctly.  Unfortunately, with the introduction of GCC
3.x,
> things are in a state of flux on both ends, and it will take some
time
> until debugging serious C++ programs becomes reasonably possible
again.

What I would _really_ like is a little animated flowchart which is
shown alongside the source :)

- Raw text -