From: Jonah Graham <jonah@kichwacoders.com>
To: psmith@gnu.org
Cc: GDB Development <gdb@sourceware.org>
Subject: Re: Debugging in multithreaded systems
Date: Thu, 06 Feb 2020 22:25:00 -0000 [thread overview]
Message-ID: <CAPmGMvjvmCGVmSLymV9Govqc1w4-_qT1pFJPFLeKpZNnqePAyw@mail.gmail.com> (raw)
In-Reply-To: <2a0eff24d5b58db30efc9d8a16b256f4748d0071.camel@gnu.org>
On Thu, 6 Feb 2020 at 17:06, Paul Smith <psmith@gnu.org> wrote:
> Can someone provide some insight on multithreaded debugging?
>
I'll try - but I can't answer your underlying question about changing next
behaviour in this case.
1. Consider using non-stop mode instead of all-stop mode if supported:
https://sourceware.org/gdb/current/onlinedocs/gdb/Non_002dStop-Mode.html#Non_002dStop-Mode
-
the key line is this:
"In non-stop mode, all execution commands apply only to the current thread
by default. That is, continue only continues one thread. To continue all
threads, issue continue -a or c -a." - so you can interrupt all threads,
and then just debug the one problematic thread. If course you need a system
that supports non-stop and I don't know which ones do and don't.
2. Try passing numeric argument to step to step multiple times at once.
HTH
Jonah
prev parent reply other threads:[~2020-02-06 22:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 22:06 Paul Smith
2020-02-06 22:25 ` Jonah Graham [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=CAPmGMvjvmCGVmSLymV9Govqc1w4-_qT1pFJPFLeKpZNnqePAyw@mail.gmail.com \
--to=jonah@kichwacoders.com \
--cc=gdb@sourceware.org \
--cc=psmith@gnu.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