From: Elena Zannoni <ezannoni@redhat.com>
To: "Martin M. Hunt" <hunt@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: very very slow symbol searches
Date: Wed, 22 Jan 2003 15:02:00 -0000 [thread overview]
Message-ID: <15918.45982.254578.620499@localhost.redhat.com> (raw)
In-Reply-To: <1043236817.32119.7.camel@Dragon>
Martin M. Hunt writes:
> Anyone have any idea why search_symbols in symtab.c is now a few
> thousand times slower than it used to be? At least it is on Linux x86.
>
> Insight calls search_symbols twice on startup. Sometime 2-4 weeks ago,
> (builds from CVS on sources) Insight started taking a minute or two to
> load when debugging itself. It is very fast when debugging small
> programs, but large things like insight or gdb take forever. At first
> glance the problem is that search_symbols() is taking 20-30 seconds to
> return.
there have been some changes to that function on 12-23. Could you try
backing those out? This was a change we convinced ourselves it was ok
to do, but maybe it is problematic.
Another change was to find_pc_sect_line, not sure if that would have
an impact.
Elena
>
> Everything is fine on Windows which starts up much faster than Linux,
> even before this latest slowness.
>
> Martin
>
>
>
next prev parent reply other threads:[~2003-01-22 15:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 11:58 Martin M. Hunt
2003-01-22 15:02 ` Elena Zannoni [this message]
2003-01-22 17:41 ` David Carlton
2003-01-22 19:36 ` Andrew Cagney
2003-01-22 20:46 ` Martin M. Hunt
2003-01-23 1:14 ` Martin M. Hunt
2003-01-23 1:45 ` Daniel Jacobowitz
2003-01-23 2:43 ` Martin M. Hunt
2003-01-23 6:10 ` Eli Zaretskii
2003-01-23 16:54 ` Daniel Jacobowitz
2003-01-23 20:06 ` Andrew Cagney
2003-01-22 18:26 ` David Carlton
2003-01-22 18:44 ` David Carlton
2003-01-26 7:48 ` Martin M. Hunt
2003-01-27 17:03 ` 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=15918.45982.254578.620499@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=hunt@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