Xref:	news-dnh.mv.net comp.os.msdos.djgpp:380
Path:	news-dnh.mv.net!mv!news.sprintlink.net!demon!plug.news.pipex.net!soap.pipex.net!pipex!sunsite.doc.ic.ac.uk!nntp0.brunel.ac.uk!strath-cs!ftel.co.uk!bham!bhamcs!news.ox.ac.uk!sable.ox.ac.uk!ball0079
From:	ball0079 AT sable DOT ox DOT ac DOT uk (Matthew Biddulph)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Debugging C++ programs compiled by djgpp?
Date:	13 Jun 1995 22:03:17 GMT
Organization:	Oxford University, England
Lines:	26
References:	<3rhb3s$ba6 AT news DOT ox DOT ac DOT uk> <3rjnbt$lte AT mserv1 DOT dl DOT ac DOT uk>
Nntp-Posting-Host:	sable.ox.ac.uk
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway:	from newsgroup comp.os.msdos.djgpp

In article <3rjnbt$lte AT mserv1 DOT dl DOT ac DOT uk>,
I. Badcoe <mbbad AT s-crim1 DOT dl DOT ac DOT uk> wrote:
>Matthew Biddulph (ball0079 AT sable DOT ox DOT ac DOT uk) wrote:

[stuff about ladybug not seeing C++ symbols cut]

>
>: 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've solved the problem now - it wasn't a problem with C++ at all,
really - it's just that I had called my C++ program 'rotate.cpp',
whereas unix-style programs like gcc expect 'rotate.cc'. So Ladybug
was instructed by gcc to look for rotate.cc, and didn't find it. So I
got no source code in my disassembly.

However, as far as I can see, Ladybug doesn't specifically support
C++, so it won't let you view class structures, etc. But its current
functionality is enough for me for now.

Matt.

- Raw text -