Xref: news2.mv.net comp.os.msdos.djgpp:3644
From: elric AT wheel DOT ucdavis DOT edu (Jeffrey Taylor)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Lots of Q's
Date: 8 May 1996 18:45:20 GMT
Organization: Davis Community Network - Davis, California, USA
Lines: 39
Message-ID: <4mqq40$gmi@mark.ucdavis.edu>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 960508170427 DOT 18314D-100000 AT is>
NNTP-Posting-Host: wheel.dcn.davis.ca.us
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Eli Zaretskii (eliz AT is DOT elta DOT co DOT il) wrote:

: On 8 May 1996, Jeffrey Taylor wrote:

: > and wade thru all the members.  Printing class static variables requires 
: > figuring out the mangled name.  Not graceful or seamless, but useable.  I 
: > have debugged 10s of thousands of lines this way.

: Don't the various demangling options (like `set print demangle', `set
: demangle-style' etc.) work with DJGPP executables?  The docs don't say
: which formats support them. 

It is a little tricky, but info gdb sheds some light.  For example:

b CMPForward::go<CR>

reports that CMPForward has no method go.  It does.

b CMPForward::go<TAB><TAB>

lists all the go functions with mangled names.

b 'CMPForward::go<TAB><TAB>

and

b 'CMPForward::go()'

behave as expected.  Note the single quote!

Jeff T


-

============================================
Without my guitar, I am a poet without arms.
                        - Michael Bloomfield
============================================