From: Daniel Jacobowitz <drow@mvista.com>
To: John Firebaugh <jfirebaugh@kde.org>
Cc: gdb@sources.redhat.com
Subject: Re: 5.1 extremely slow
Date: Sun, 10 Mar 2002 11:23:00 -0000 [thread overview]
Message-ID: <20020310142305.A3635@nevyn.them.org> (raw)
In-Reply-To: <200203101103.39102.jfirebaugh@kde.org>
On Sun, Mar 10, 2002 at 11:03:39AM -0800, John Firebaugh wrote:
> On Sunday 10 March 2002 10:47, John Firebaugh wrote:
> > I've upgraded to 5.1.1 due to bugs in 4.x, but debugging almost any program
> > is unbearably slow. I've attached some detailed debug output; here is a
> > summary:
>
> Update: this is probably the same problem discussed in the thread "gdb and
> dlopen":
>
> http://sources.redhat.com/ml/gdb/2001-10/msg00157.html
>
> Is there a fix for this yet?
Not yet. It's a tricky problem, because we lose the ability to set
breakpoints in early functions in shared libraries if we fix it.
You aren't seeing that problem specifically as much as the hideous
performance of the threads package. There's no way to disable thread
debugging (should we add a set for that? I think we should!) but you
can temporarily remove or make unreadable /lib/libthread_db.so.1 to
disable it. It will automatically kick in if you are linked to
-lpthread.
We need to address some of the performance concerns of this code very
badly. I have a few ideas but they will not be in time for 5.2.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-03-10 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-10 10:48 John Firebaugh
2002-03-10 11:04 ` John Firebaugh
2002-03-10 11:23 ` Daniel Jacobowitz [this message]
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=20020310142305.A3635@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=jfirebaugh@kde.org \
/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