From: Daniel Jacobowitz <drow@mvista.com>
To: wim delvaux <wim.delvaux@adaptiveplanet.com>
Cc: Andrew Cagney <ac131313@redhat.com>, gdb@sources.redhat.com
Subject: Re: why is gdb 5.2 so slow
Date: Fri, 01 Nov 2002 07:17:00 -0000 [thread overview]
Message-ID: <20021101151742.GB3924@nevyn.them.org> (raw)
In-Reply-To: <20021101151511.QPTX1218.amsfep11-int.chello.nl@there>
On Fri, Nov 01, 2002 at 04:15:17PM +0100, wim delvaux wrote:
>
> > Can you file a bug? http://sources.redhat.com/gdb/bugs/ Yes, that
> > would quickly become frustrating.
>
> Done ... example attached
>
> >
> > A workaround is to add `set height 0' to your .gdbinit file.
>
> Will try that, thanx. Indeed the number of prompts is related to
> the window size.
>
> >
> > I think you won the lottery in finding GDB's current known worst case :-)
>
> If I look at your explanation i think indeed I have the EXTREME situation
> here. I can easily have about 10 threads and about 60 dynamically loaded
> libraries and as said my PC is NOT the most powerfull ;-(
>
> Thanx again for the reply
Knew I forgot to suggest something.
If you don't need watchpoint support, please try running your program
under gdbserver instead of directly in GDB. It should be buckets
faster.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-11-01 15:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 17:32 wim delvaux
2002-10-31 19:51 ` Daniel Jacobowitz
2002-11-01 5:31 ` wim delvaux
2002-11-01 6:58 ` Andrew Cagney
2002-11-01 7:15 ` wim delvaux
2002-11-01 7:17 ` Daniel Jacobowitz [this message]
2002-11-01 8:13 ` wim delvaux
2002-11-01 7:15 ` Daniel Jacobowitz
2002-11-01 8:55 ` Andrew Cagney
2002-11-01 10:14 ` Daniel Jacobowitz
2002-11-01 10:32 ` Andrew Cagney
2002-11-01 10:44 ` Kevin Buettner
[not found] ` <redirect-4290038@silicondust.com>
2002-11-01 8:36 ` Nick Kelsey
2002-11-01 11:43 Howell, David P
2002-11-01 12:46 ` Andrew Cagney
2002-11-04 12:44 ` Jim Blandy
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=20021101151742.GB3924@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=wim.delvaux@adaptiveplanet.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