Xref: news-dnh.mv.net comp.os.msdos.djgpp:344
Path: news-dnh.mv.net!mv!news.sprintlink.net!pipex!sunsite.doc.ic.ac.uk!daresbury!s-crim1!mbbad
From: mbbad AT s-crim1 DOT dl DOT ac DOT uk (I. Badcoe)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Debugging C++ programs compiled by djgpp?
Date: 13 Jun 1995 09:56:13 GMT
Organization: SERC Daresbury Lab, Warrington, U.K.
Lines: 33
References: <3rhb3s$ba6 AT news DOT ox DOT ac DOT uk>
Nntp-Posting-Host: s-crim1.dl.ac.uk
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

Matthew Biddulph (ball0079 AT sable DOT ox DOT ac DOT uk) wrote:
: Do any of the debuggers currently available for djgpp fully support
: C++ programs? I have tried both Ladybug and FSDB (which, incidentally,
: I think are great tools), but neither seems to be able to cope with
: symbols in C++. After compiling with '-g', rather than the appropriate
: lines of code appearing in the assembly listings, I get either blank
: lines or strange garbage. Presumably this is something to do with C++
: name-mangling. Apart from this problem, debugging appears to work
: correctly.

: Can anyone suggest a debugger (or a fix) that will work?

I also would like to be able to do this but cannot as yet.

According to the gdb documentation, gdb can only correctly handle C++
correctly if the object modules are compiled in stabs (or maybe stabs+)
format.  Unfortunately djgpp doesn't support stabs format.

(i) Will V2 support more object formats ?

(ii) If not, how difficult would it be to add stabs format, is it just a
	matter of uncommenting some lines in the source, or is it hours
	of head-scratching frustration ?

(iii) (This just occured to me.)  Objcopy can change formats, presumeably,
	even if it would do the conversion, the required debugging information
	would still be missing in the new file.

Anybody know ?

	Badders