public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: David Carlton <carlton@math.stanford.edu>,
	gdb <gdb@sources.redhat.com>, Elena Zannoni <ezannoni@redhat.com>,
	Jim Blandy <jimb@redhat.com>
Subject: Re: [rfc] struct dictionary
Date: Fri, 25 Apr 2003 02:22:00 -0000	[thread overview]
Message-ID: <20030425022223.GA11069@nevyn.them.org> (raw)
In-Reply-To: <3EA89AB3.6050403@redhat.com>

On Thu, Apr 24, 2003 at 10:17:23PM -0400, Andrew Cagney wrote:
> 
> >Blocks currently store symbols in one of three different ways: using a
> >hash table, using an unsorted list, or using a sorted list.  Most
> >blocks are built by buildsym.c, which use only the former two
> >mechanisms.  Sorted list blocks are only being produced by
> >mdebugread.c.  And, to make matters worse, jv-lang.c produces one
> >unsorted list block for which the predicate BLOCK_SHOULD_SORT matches;
> >the chain of events by which GDB actually treats that block correctly
> >is very tenuous.
> 
> Um, didn't BLOCK_SHOULD_SORT get deleted?

Nope, just used less.  It's not deleted for the reasons David
describes.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2003-04-25  2:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-16 20:05 David Carlton
2003-04-25  2:17 ` Andrew Cagney
2003-04-25  2:22   ` Daniel Jacobowitz [this message]
2003-04-25  4:35   ` David Carlton
2003-04-25 15:31     ` Andrew Cagney
2003-04-25 16:38       ` David Carlton
2003-05-01 23:09         ` Andrew Cagney
2003-05-10 18:09           ` Andrew Cagney
2003-06-03  2:20             ` Elena Zannoni
2003-06-03  3:00               ` David Carlton
2003-04-29 15:10     ` Andrew Cagney
2003-04-29 19:16       ` David Carlton
2003-04-29 20:06         ` Andrew Cagney
2003-04-29 20:39           ` 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=20030425022223.GA11069@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@redhat.com \
    --cc=carlton@math.stanford.edu \
    --cc=ezannoni@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).