From: Sergey Zigachev via Gdb <gdb@sourceware.org>
To: gdb@sourceware.org
Subject: Re: Multi-threading support on DragonFlyBSD
Date: Sun, 9 Mar 2025 20:16:37 +0500 [thread overview]
Message-ID: <AS8PR05MB8230E8AB1FD0D4B3D8D0ECCD92D72@AS8PR05MB8230.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <DB9PR05MB82353E274191A69996FF924D92CB2@DB9PR05MB8235.eurprd05.prod.outlook.com>
Ok, skimmed through linux target I saw this:
/* In all-stop, give preference to the LWP that is being
single-stepped. There will be at most one, and it will be the
LWP that the core is most interested in. If we didn't do this,
then we'd have to handle pending step SIGTRAPs somehow in case
the core later continues the previously-stepped thread, as
otherwise we'd report the pending SIGTRAP then, and the core, not
having stepped the thread, wouldn't understand what the trap was
for, and therefore would report it to the user as a random
signal. */
I guess this answers my question.
next prev parent reply other threads:[~2025-03-09 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 10:22 Sergey Zigachev via Gdb
2025-03-09 15:16 ` Sergey Zigachev via Gdb [this message]
2025-03-10 16:22 ` Simon Marchi via Gdb
2025-03-11 7:59 ` Sergey Zigachev via Gdb
2025-03-11 14:37 ` Simon Marchi via Gdb
2025-03-12 4:12 ` Sergey Zigachev via Gdb
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=AS8PR05MB8230E8AB1FD0D4B3D8D0ECCD92D72@AS8PR05MB8230.eurprd05.prod.outlook.com \
--to=gdb@sourceware.org \
--cc=s.zi@outlook.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