From: Michael Snyder <msnyder@redhat.com>
To: Will Cohen <wcohen@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Slow handling of C++ symbol names
Date: Thu, 20 Nov 2003 02:05:00 -0000 [thread overview]
Message-ID: <3FBC217A.40105@redhat.com> (raw)
In-Reply-To: <3FBBDC27.50204@redhat.com>
Will Cohen wrote:
> When debugging some C++ program with gdb (both versions 5.3 and 6.0) it
> takes a long time to load the debugging information and get a
> command-line prompt. The particular example that demonstrates this
> problem is monotone (http://www.venge.net/monotone/) which makes use of
> the boost libraries (http://www.boost.org/). gdb loading monotone with
> the associated debugging information takes over 30 seconds to get the
> initial command-line prompt on a 1.7GHz Athlon with 512MB or DRAM.
30 seconds! Why, you young whipper-snapper... I remember when you
used to have to go get a cup of coffee while gdb loaded symbols! ;-)
Hell, sometimes you could go out and *buy* the coffee...
next prev parent reply other threads:[~2003-11-20 2:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 21:10 Will Cohen
2003-11-19 22:10 ` Daniel Berlin
2003-11-20 2:05 ` Michael Snyder [this message]
2003-11-20 14:27 ` Will Cohen
2003-11-20 20:22 ` Michael Snyder
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=3FBC217A.40105@redhat.com \
--to=msnyder@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=wcohen@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