From: Basile Starynkevitch <basile@starynkevitch.net>
To: Andrew Burgess <aburgess@redhat.com>, 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 13:29:31 +0200 [thread overview]
Message-ID: <cda4f594beff169e12f566192be1a95d3daf0ad3.camel@starynkevitch.net> (raw)
In-Reply-To: <87plganni8.fsf@redhat.com>
On Thu, 2025-05-15 at 12:04 +0100, Andrew Burgess via Gdb wrote:
> 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.
Thanks. Do you mind explaining how that works? or in what GDB source files does
that happen?
RefPerSys is generating dynamically code with libgccjit and GNU lightning....
Thanks.
--
Basile STARYNKEVITCH <basile@starynkevitch.net>
8 rue de la Faïencerie http://starynkevitch.net/Basile/
92340 Bourg-la-Reine https://github.com/bstarynk
France https://github.com/RefPerSys/RefPerSys
next prev parent reply other threads:[~2025-05-15 11:30 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
2025-05-15 11:29 ` Basile Starynkevitch [this message]
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=cda4f594beff169e12f566192be1a95d3daf0ad3.camel@starynkevitch.net \
--to=basile@starynkevitch.net \
--cc=Gdb@sourceware.org \
--cc=aburgess@redhat.com \
--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