From: Michael Snyder <Michael.Snyder@palmsource.com>
To: David Highley <dhighley@highley-recommended.com>
Cc: gdb@sourceware.org
Subject: Re: Break in a thread but continue other threads
Date: Wed, 21 Feb 2007 01:10:00 -0000 [thread overview]
Message-ID: <1172019238.19657.75.camel@localhost.localdomain> (raw)
In-Reply-To: <200702161602.l1GG2gpr014571@douglas.highley-recommended.com>
On Fri, 2007-02-16 at 08:02 -0800, David Highley wrote:
> Is it possible to put a break in one thread but continue all the other
> threads?
No, gdb has a very simple model for thread debugging:
either all threads are running, or all are stopped.
* Except as noted below...
> Our developers keep lamenting to me the inadequacies of the gdb
> debugger in debugging our run time configured multi-threaded
> applications. In several cases I can answer read the manual but in
> others I know the persons diligence and capabilities. While ddd is ok it
> would not be considered a great interface by any standard. I peronally
> am not complaining as I do not use any of the integrated development
> environments but I get plenty of input from the developer community;
> 300+ on just one program.
* Theoretically, you might set a thread-specific breakpoint
and attach to it the command "set scheduler-locking on".
If your host / target supports scheduler locking, this
would prevent any other thread from running, whereupon
you could simply "continue".
However, use at your own risk... it's a great way to
create a deadlock. I haven't tried this, usual disclaimers
apply...
prev parent reply other threads:[~2007-02-21 0:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 16:06 David Highley
2007-02-16 17:19 ` Daniel Jacobowitz
2007-02-17 10:37 ` Nicholas Mc Guire
2007-02-17 13:16 ` Eli Zaretskii
2007-02-17 13:51 ` Nicholas Mc Guire
2007-02-21 1:10 ` Michael Snyder [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=1172019238.19657.75.camel@localhost.localdomain \
--to=michael.snyder@palmsource.com \
--cc=dhighley@highley-recommended.com \
--cc=gdb@sourceware.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