From: David Carlton <carlton@math.stanford.edu>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [dictionary] commit for 2003-03-06
Date: Fri, 07 Mar 2003 18:01:00 -0000 [thread overview]
Message-ID: <ro1d6l3f44m.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <ro1llzrf79v.fsf@jackfruit.Stanford.EDU>
On 07 Mar 2003 08:53:00 -0800, David Carlton <carlton@math.stanford.edu> said:
> And there might be uses elsewhere, too: I haven't yet audited all the
> uses of lookup_minimal_symbol. I'm fairly sure that the symbol lookup
> functions in symtab.c are safe, from memory, and there shouldn't be
> _too_ many other places that want a natural name when looking at
> minimal symbols, but there might be some.
In fact, there are: the .y files all have likely candidates, and I
want to look more closely at a handful of other uses (in remote.c,
printcmd.c, objc-lang.c, and valops.c). So the demangled hash table
definitely stays.
Which raises another interesting issue: should whatever of those uses
turn out to want natural names also accept linkage names? I'm
reluctantly starting to think that they should. They typically call
lookup_minimal_symbol with a string taken from user input; in an ideal
world, I think it would be reasonable to not allow users to get at
stuff via linkage names, but there have been enough C++ bugs that can
be worked around if you know the linkage name that I don't think we're
there yet. Hmm; I'll have to think about what internal interface I
like, given that desire.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2003-03-07 18:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 0:53 David Carlton
2003-03-07 14:40 ` Daniel Jacobowitz
2003-03-07 16:53 ` David Carlton
2003-03-07 18:01 ` David Carlton [this message]
2003-03-07 14:58 ` Andrew Cagney
2003-03-07 17:08 ` David Carlton
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=ro1d6l3f44m.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