From: <chris.hall.list@highwayman.com>
To: <gdb@sourceware.org>
Subject: RE: How to switch threads in gdb while a thread is being blocked
Date: Wed, 30 Mar 2011 00:03:00 -0000 [thread overview]
Message-ID: <02ff01cbee6d$e9116b70$bb344250$@highwayman.com> (raw)
In-Reply-To: <m34o6motlx.fsf@fleche.redhat.com>
Tom Tromey wrote (on Tue 29-Mar-2011 at 16:05):
....
> >>>>> "Alexandru" == Alexandru Sutii <sutii.alex@gmail.com> writes:
>
> Alexandru> Is there a way to switch threads in gdb after the current
> Alexandru> thread/process blocks?
>
> You want target-async. See the "Background Execution" node in the
> manual; there are corresponding MI commands (and docs) too. You may
> also want non-stop.
Though my experience with non-stop is that it crashes and burns when
you single step through the end of some functions :-(
Chris
next prev parent reply other threads:[~2011-03-30 0:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 20:45 Alexandru Sutii
2011-03-29 15:05 ` Tom Tromey
2011-03-29 21:59 ` Alexandru Sutii
2011-03-30 0:03 ` chris.hall.list [this message]
2011-03-30 13:58 ` Tom Tromey
2011-03-30 15:16 ` 'Chris Hall'
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='02ff01cbee6d$e9116b70$bb344250$@highwayman.com' \
--to=chris.hall.list@highwayman.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