From: Andrew Burgess via Gdb <gdb@sourceware.org>
To: Basile Starynkevitch <basile@starynkevitch.net>, Gdb@sourceware.org
Cc: team@refpersys.org
Subject: Re: GDB process (on Linux) cooperating with the debugged process (some particular pthread on it)
Date: Thu, 15 May 2025 12:04:31 +0100 [thread overview]
Message-ID: <87plganni8.fsf@redhat.com> (raw)
In-Reply-To: <b14f6386886f7343e58dd2b02f5445c7bab45491.camel@starynkevitch.net>
Basile Starynkevitch <basile@starynkevitch.net> writes:
> Hello all,
>
> Is it possible for the debugged process (for me the RefPerSys inference engine,
> GPL licensed, see below) which has several threads to send GDB commands or
> interact with the debugger process.
I'm not aware of any existing, general technique for having the debuggee
send commands to the debugger. There is some limited support for JIT
like processes to allow the process to give GDB debug information for
the dynamically generated code, but nothing beyond that.
>
> This on Linux only (often x86-64, kernel 6.12.27); some event loop of the
> debugged process could run in a particular pthread (which I don't want to debug
> with such a weird GDB).
>
> In general help on debugging a multithreaded Linux process is welcome. Can I
> stop (or GDB step) only one thread and let the others run?
You can turn on non-stop mode with 'set non-stop on'. In non-stop mode,
when one thread stops, other threads are left running.
HTH
Thanks,
Andrew
next prev parent reply other threads:[~2025-05-15 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 9:12 Basile Starynkevitch
2025-05-15 11:04 ` Andrew Burgess via Gdb [this message]
2025-05-15 11:29 ` Basile Starynkevitch
2025-05-16 9:54 ` Andrew Burgess 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=87plganni8.fsf@redhat.com \
--to=gdb@sourceware.org \
--cc=aburgess@redhat.com \
--cc=basile@starynkevitch.net \
--cc=team@refpersys.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