From: "Andrew Crabtree" <andrewc AT rosemail DOT rose DOT hp DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Source Level Debugging C++ Templates
Date: 21 Aug 1997 23:58:02 GMT
Organization: Hewlett Packard
Lines: 25
Message-ID: <01bcae8e$3711be30$45111d0f@ros51675cra>
References: <33fc5661 DOT 107598 AT news DOT datacomm DOT ch>
NNTP-Posting-Host: ros51675cra.rose.hp.com
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk



Heribert Slama <hslama AT datacomm DOT ch> wrote in article
<33fc5661 DOT 107598 AT news DOT datacomm DOT ch>...
> I didn't try the stand-alone debugger GDB; I probably never will.
> Frankly, I don't want to learn a command line driven source level
> debugger. Even if GDB could handle included source text, I would hate
> to use it. I know, with Emacs use of GDB is much easier, but my PC
> seems just a bit too small for that (486/33, 12MB RAM).
GDB isn't that bad.  As long as you remember the function names you used
its pretty easy. 
You can do a lot with p(rint) s(tep) n(ext) and b(reak) bt(race) and
f(rame)
 
> - there is another combination of compiler options and module
> organization, that will do the job.
my guess is that if you compile with -gstabs instead of -g it will allow
you to debug as 
you want.  Unfortunately, unless you are using pgcc, your compiler will not
support it.
Go to http://www.goof.com/pcg/ to try it.  Alternatively, go to SETs home
page, patch the gcc
sources, and rebuild.

Andrew