From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [dictionary] commit for 2003-03-06
Date: Fri, 07 Mar 2003 14:40:00 -0000 [thread overview]
Message-ID: <20030307144017.GA20963@nevyn.them.org> (raw)
In-Reply-To: <ro1y93sf15j.fsf@jackfruit.Stanford.EDU>
On Thu, Mar 06, 2003 at 04:52:56PM -0800, David Carlton wrote:
> Following Andrew's lead, I'm going to try to remember to post my
> commits to carlton_dictionary-branch. They won't always be the
> prettiest commits: I usually commit once at the end of each day that
> I've done any work on the branch, assuming that I leave it in a
> working state (which I almost always do!); this means that a commit
> may contain something that I plan to continue the next day, and it
> also may contain bits of unrelated tasks that I'm working on. Also,
> the ChangeLogs aren't great: they're written in a way that is easy to
> generate, as opposed to a way that is easiest to review years in the
> future. (I'm much more careful with the ChangeLogs on the mainline,
> don't worry!)
>
> This branch has as its primarily task to improve C++ namespace
> support; it also contains cleanups related to symbol names, linespec,
> and const correctness. (All of which I intend to move to the
> mainline; I'm doing so gradually.) It's probably not as focussed a
> branch as Andrew would like; it works for me, though.
>
> Today's commits are the start of cleaning up minimal symbol names and
> accessors (which will be an ongoing task), and fixes a few (but not
> all) FAILing regexps in gdb.c++/templates.exp (also ongoing, though
> actually I think I'm more likely to try to get rid of the differences
> in behavior rather than make the regexps more generous).
>
> 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.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-03-07 14:40 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 [this message]
2003-03-07 16:53 ` David Carlton
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=20030307144017.GA20963@nevyn.them.org \
--to=drow@mvista.com \
--cc=carlton@math.stanford.edu \
--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