From: David Carlton <carlton@math.stanford.edu>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA/symtab: (Almost) always hash blocks when searching them
Date: Mon, 10 Feb 2003 19:14:00 -0000 [thread overview]
Message-ID: <ro1adh4j6cs.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <20030209220321.GA19572@nevyn.them.org>
On Sun, 9 Feb 2003 17:03:21 -0500, Daniel Jacobowitz <drow@mvista.com> said:
> I'm working on modifying the symbol lookup functions to return
> multiple symbols when there are multiple possible matches, and I
> didn't want to have to modify all three kinds of binary search in
> lookup_block_symbol. First I tried fixing mdebugread.c to generate
> hashed blocks properly; it was too messy, and I couldn't build an
> mdebug toolchain to test with [mips-ecoff was my best guess, and
> it's been broken for months. Part of it was my fault and then GCC
> started segfaulting after I fixed that].
For what it's worth (I do realize you've withdrawn your patch), I'm
hoping to submit an RFC by the end of February for a plan that will
include getting rid of sorted linear blocks. I'm not up for
buildsymifying mdebugread.c, but I'm up for doing that amount of
cleanup.
I haven't looked at your patch, but one piece of trivia that you might
want to be aware of if my RFC is rejected and if you have to deal with
this again is that Java code will create one block that is a
non-sorted linear block but that isn't associated to a function. It's
easy to screw that one up without realizing it; if you do, Tom Tromey
will get mad at you. :-)
David Carlton
carlton@math.stanford.edu
prev parent reply other threads:[~2003-02-10 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-09 22:03 Daniel Jacobowitz
2003-02-09 22:37 ` Daniel Jacobowitz
2003-02-10 19:14 ` David Carlton [this message]
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=ro1adh4j6cs.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