From: "Eli Zaretskii" <eliz@elta.co.il>
To: Andrew Cagney <cagney@gnu.org>
Cc: drow@false.org, ezannoni@redhat.com, carlton@kealia.com,
gdb@sources.redhat.com
Subject: Re: Huge slowdown since 6.0
Date: Sat, 21 Feb 2004 09:04:00 -0000 [thread overview]
Message-ID: <2914-Sat21Feb2004110216+0200-eliz@elta.co.il> (raw)
In-Reply-To: <403655D4.1020102@gnu.org> (message from Andrew Cagney on Fri, 20 Feb 2004 13:45:40 -0500)
> Date: Fri, 20 Feb 2004 13:45:40 -0500
> From: Andrew Cagney <cagney@gnu.org>
>
> If we knew for instance that only 10% of users set breakpoints outside
> of the main executible, then we'd also know that we were frustrating 90%
> of users by making them sit around waiting for needless symbol table
> reads :-(
I think we can say we know this already. I'm quite sure that the
number of users who set breakpoints outside their program's code is
miniscule, much less than 10%.
> On the other hand, if we knew that the first thing people did was:
> (gdb) break <tab>
> we'd have an entirely different problem.
I think "break TAB" is very rare. But "info address", "info symbol",
and their ilk might be much more popular. However, it is IMHO
entirely reasonable to load the full symbol table when such commands
are issued. I'd even print a message, something like
Loading symbols for your_monster_proggy; this could take a while..."
next prev parent reply other threads:[~2004-02-21 9:04 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 [this message]
2004-02-21 2:18 ` Daniel Jacobowitz
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=2914-Sat21Feb2004110216+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=cagney@gnu.org \
--cc=carlton@kealia.com \
--cc=drow@false.org \
--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