From: David Carlton <carlton@math.stanford.edu>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] annotate blocks with C++ namespace information
Date: Tue, 11 Mar 2003 22:59:00 -0000 [thread overview]
Message-ID: <ro1zno1o6hb.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <ro165qpplrs.fsf@jackfruit.Stanford.EDU>
On 11 Mar 2003 14:43:19 -0800, David Carlton <carlton@math.stanford.edu> said:
> On Tue, 11 Mar 2003 16:23:13 -0500, Daniel Jacobowitz <drow@mvista.com> said:
>> On Tue, Mar 11, 2003 at 01:14:16PM -0800, David Carlton wrote:
>>> Do any demanglers put in spaces after 'operator'? I hope not...
>> I thought one of them did, but I might have been mistaken.
> You could easily be right: I haven't done a lot of GCC v2 checking.
> I'll look into that, and, if so, add a guard for a possible extra
> space in cp_find_first_component.
Yeah, I'll add it: with gcc 2.95.3 -gdwarf-2, I get:
.ascii "operator ->\0" # DW_AT_name
.byte 0x1 # DW_AT_decl_file
.byte 0x3 # DW_AT_decl_line
.ascii "__rf__1C\0" # DW_AT_MIPS_linkage_name
and while the demangler doesn't put in a space when demangling
__rf__1C, there's still that space in the DW_AT_name. And while I
think that most internal uses of operator names within GDB will come
via the demangler, it's probably not wise to bet that they all do.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2003-03-11 22:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-22 1:47 David Carlton
2003-03-11 17:11 ` Daniel Jacobowitz
2003-03-11 21:14 ` David Carlton
2003-03-11 21:23 ` Daniel Jacobowitz
2003-03-11 22:43 ` David Carlton
2003-03-11 22:59 ` David Carlton [this message]
2003-03-11 23:01 ` Daniel Jacobowitz
2003-03-17 22:33 ` David Carlton
2003-04-14 19:22 ` Elena Zannoni
2003-04-14 21:33 ` David Carlton
2003-04-15 2:08 ` Daniel Jacobowitz
2003-04-15 2:26 ` Elena Zannoni
2003-04-15 3:07 ` David Carlton
2003-04-15 23:12 ` David Carlton
2003-04-16 1:22 ` Elena Zannoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ro1zno1o6hb.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox