Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: Andrew Cagney <cagney@gnu.org>,
	David Carlton <carlton@kealia.com>,
	gdb@sources.redhat.com
Subject: Re: Huge slowdown since 6.0
Date: Sat, 21 Feb 2004 02:18:00 -0000	[thread overview]
Message-ID: <20040221021856.GB19335@nevyn.them.org> (raw)
In-Reply-To: <16438.18096.205403.553354@localhost.redhat.com>

On Fri, Feb 20, 2004 at 12:41:04PM -0500, Elena Zannoni wrote:
> The thing that I am curious about is to see how early into a regular
> debug session we build the symtabs. I.e. I am afraid that any
> reference to any symbol from the command line makes the whole lot
> expand anyway. The answer to this may help answer the question whether
> we really need a two tier symbol table system, or if there is another
> way of solving the same problem. While cleaning up the obstack stuff,
> it became obvious that the intent was for the psymtabs to go away once
> expanded into full symtabs, but this was never implemented.

From the last time I looked at this issue (a while ago, now): when a
symbol is referenced on the command line we generally build symtabs for
the symbol containing it.  We do not build all symtabs for its object;
we used to do that for some C++ operations (overload checking maybe?)
and it was extremely noticeable.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  parent reply	other threads:[~2004-02-21  2:18 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-18 21:09 Daniel Jacobowitz
2004-02-18 21:31 ` David Carlton
2004-02-18 22:45   ` Kip Macy
2004-02-19  3:35     ` Daniel Jacobowitz
2004-02-19  5:06       ` Kip Macy
2004-02-19 15:40         ` Daniel Jacobowitz
2004-02-20  5:09   ` Daniel Jacobowitz
2004-02-20 16:42     ` Elena Zannoni
2004-02-20 16:47       ` Daniel Jacobowitz
2004-02-20 17:33         ` Elena Zannoni
2004-02-20 17:01       ` Andrew Cagney
2004-02-20 17:05         ` Daniel Jacobowitz
2004-02-20 17:45         ` Elena Zannoni
2004-02-20 18:07           ` Andrew Cagney
2004-02-20 18:24             ` Daniel Jacobowitz
2004-02-20 18:45               ` Andrew Cagney
2004-02-20 18:48                 ` Daniel Jacobowitz
2004-02-21  9:21                   ` Eli Zaretskii
2004-02-21  9:04                 ` Eli Zaretskii
2004-02-21  2:18           ` Daniel Jacobowitz [this message]
2004-02-20 16:52     ` David Carlton
2004-02-20 16:58       ` Daniel Jacobowitz
2004-02-20 17:00         ` David Carlton
2004-02-20 17:35       ` Elena Zannoni
2004-02-19  1:59 ` Elena Zannoni
2004-02-19  3:35   ` Daniel Jacobowitz
2004-02-19  3:58     ` Daniel Jacobowitz
2004-02-20 19:57 Michael Elizabeth Chastain
2004-02-23 19:22 ` Andrew Cagney

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=20040221021856.GB19335@nevyn.them.org \
    --to=drow@false.org \
    --cc=cagney@gnu.org \
    --cc=carlton@kealia.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb@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