From: Daniel Jacobowitz <drow@mvista.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Select a particular mangling of a demangled symbol in lookup_block_symbol
Date: Fri, 22 Mar 2002 10:52:00 -0000 [thread overview]
Message-ID: <20020322135219.B24693@nevyn.them.org> (raw)
In-Reply-To: <15511.47485.557533.258275@localhost.redhat.com>
On Tue, Mar 19, 2002 at 05:19:41PM -0500, Elena Zannoni wrote:
> OK, approved. But I have my usual couple of questions:
Committed to trunk only; I'll move it to the branch in a week or so if
it doesn't break anything.
> Was the corresponding testsuite patch sorted out? Looks like it
> wasn't. Does this patch have any effect on the testsuite results w/o
Nope.
> the testsuite patch?
I don't believe so.
> In the above, should it be mangled_name = name or mangled_name =
> modified_name? It would seem more uniform with the rest of the
> function if we just used modified_name. Unless there is some problem
> with case sensitivity, in which case, calling cplus_demangle with
> modified_name seems wrong anyway. I.e. is it guaranteed that
> case_sensitive_off is NOT in effect? Just out of curiosity What
> would happen if the user sets the case sensitivity off?
> Wouldn't it change _ZN3fooC1ERS_ to _zn3fooc1ers_ ? (of course the user
> can always do a lot of things to screw himself up)
As far as I'm concerned - if the user sets case sensitivity off while
debugging C++, they deserve what they get. Mangling is not
case-insensitive. In fact, in v3, cplus_demangle is absolutely
guaranteed to fail (_z is not a legal prefix for a mangled name).
Perhaps it would be better to call cplus_demangle with the original
name.
> I guess what I am really asking is when is lookup_symbol called with a
> mangled name. I tried to do "break foo::foo", and I never saw it called
> with a mangled name.
find_methods will do it, in two places, at least if you're using stabs:
sym_arr[i1] = lookup_symbol (phys_name,
NULL, VAR_NAMESPACE,
(int *) NULL,
(struct symtab **) NULL);
It shouldn't do this, of course, but that requires a lot of work that I
haven't gotten to yet.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-03-22 18:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 15:55 Daniel Jacobowitz
2002-03-19 11:53 ` Daniel Jacobowitz
2002-03-19 14:25 ` Elena Zannoni
2002-03-19 14:20 ` Elena Zannoni
2002-03-19 14:47 ` Elena Zannoni
2002-03-22 10:55 ` Daniel Jacobowitz
2002-03-22 12:11 ` Elena Zannoni
2002-03-22 14:53 ` Daniel Jacobowitz
2002-03-22 10:52 ` Daniel Jacobowitz [this message]
2002-03-22 12:10 ` Elena Zannoni
2002-02-15 16:38 Michael Elizabeth Chastain
2002-02-15 16:46 ` Daniel Jacobowitz
2002-02-15 18:15 Michael Elizabeth Chastain
2002-02-16 10:59 Michael Elizabeth Chastain
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=20020322135219.B24693@nevyn.them.org \
--to=drow@mvista.com \
--cc=ezannoni@redhat.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