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 16:53:00 -0000 [thread overview]
Message-ID: <ro1llzrf79v.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <20030307144017.GA20963@nevyn.them.org>
On Fri, 7 Mar 2003 09:40:17 -0500, Daniel Jacobowitz <drow@mvista.com> said:
> On Thu, Mar 06, 2003 at 04:52:56PM -0800, David Carlton wrote:
>> Question for those of you who have read this far: now that
>> lookup_symbol_aux_minsyms is on its last legs (it's gone on the
>> branch), do you think we could get rid of the demangled hash table
>> for minsyms? I'll try to audit uses of lookup_minimal_symbol
>> tomorrow or next week.
> No. Every time you talk about removing something with minimal
> symbols, remember that we can use them to debug a program with no
> symbolic debug info.
Yeah, I think you're right. I was thinking about this last night, and
I realized that decode_line_1 is a likely culprit: it needs to do
minimal symbol lookups in order to be able to break on functions with
no debug info.
Except that, of course, the story isn't that simple: the only part of
decode_line_1 that should care whether it uses the linkage name
instead of the natural name is decode_compound, and that part of the
code currently _doesn't_ do a lookup_minimal_symbol. Sigh. So, right
now, I actually think we could get rid of the demangled hash table
without causing any problems. But I think that should probably be
considered a bug in decode_compound rather than a reason to get rid of
the demangled hash table.
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.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2003-03-07 16:53 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 [this message]
2003-03-07 18:01 ` David Carlton
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=ro1llzrf79v.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