From: "Nick Kelsey" <nickk@ubicom.com>
To: <gdb@sources.redhat.com>
Subject: Re: why is gdb 5.2 so slow
Date: Fri, 01 Nov 2002 08:36:00 -0000 [thread overview]
Message-ID: <007a01c281c4$d8beef00$0a00a8c0@nkelseyhome> (raw)
In-Reply-To: <redirect-4290038@silicondust.com>
> Both. Things we do wrong:
> - GDB can't handle being told that just one thread is stopped. If we
> could, then we wouldn't have to stop all threads for shared library
> events; there's a mutex in the system library so we don't even have to
> worry about someone hitting the breakpoint. We could also use this to
> save time on conditional breakpoints; if we aren't stopping, why stop
> all other threads?
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
We have exactly this problem at the moment - our system supports setting
breakpoints that only stop specified threads, however GDB cannot use this
support at the moment. If you have an interest for this support then I would
be interested in your thoughts.
Nick
Nick Kelsey
Senior Software Engineer
Ubicom
next prev parent reply other threads:[~2002-11-01 16:36 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 ` 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
2002-11-01 7:15 ` wim delvaux
2002-11-01 7:17 ` Daniel Jacobowitz
2002-11-01 8:13 ` wim delvaux
[not found] ` <redirect-4290038@silicondust.com>
2002-11-01 8:36 ` Nick Kelsey [this message]
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='007a01c281c4$d8beef00$0a00a8c0@nkelseyhome' \
--to=nickk@ubicom.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