From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Thiago Jung Bauermann <thiago.bauermann@gmail.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>,
Reid Kleckner <rnk@mit.edu>,
unladen-swallow@googlegroups.com
Subject: Re: [RFA] Add interface for registering JITed code
Date: Fri, 31 Jul 2009 20:55:00 -0000 [thread overview]
Message-ID: <8ac60eac0907311245p39481427y4071e5eeef655c89@mail.gmail.com> (raw)
In-Reply-To: <200907311201.28986.thiago.bauermann@gmail.com>
On Fri, Jul 31, 2009 at 8:01 AM, Thiago Jung
Bauermann<thiago.bauermann@gmail.com> wrote:
>> If/when someone wants to add another scripting language to GDB, we will be
>> bitten by this issue. I can see that happening already. :-)
>
> I still think this will happen soon enough ...
If I understand correctly what you mean, you aren't worried about adding a
new scripting language to GDB (as in, embed 'Tcl' in addition to 'Python'
into GDB), but rather about debugging inferior with two (or more) separate
JITters in it.
If I understand the patch, proposed GDB/JIT interface allows this: there
could be several (local) "__jit_debug_register_code" symbols in a
statically-linked executable, and several (possibly global)
"__jit_debug_register_code" symbols if JITters are in separate shared libs.
When this situation arises, GDB could be fixed to set a breakpoint on all
such symbols, and read data from all "__jit_debug_descriptor" symbols.
Once that's done, debugging inferior with multiple JITters will "Just
Work(TM)".
What did I miss?
Thanks,
--
Paul Pluzhnikov
prev parent reply other threads:[~2009-07-31 19:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 1:58 Reid Kleckner
2009-07-23 12:08 ` Reid Kleckner
2009-07-23 23:21 ` Tom Tromey
2009-07-24 13:25 ` Ulrich Weigand
2009-07-24 16:52 ` Doug Evans
2009-07-25 0:40 ` [unladen-swallow] " Reid Kleckner
2009-07-24 16:55 ` Reid Kleckner
2009-07-24 20:42 ` Eli Zaretskii
2009-07-24 20:55 ` Tom Tromey
2009-07-25 15:29 ` Eli Zaretskii
2009-07-27 23:20 ` Reid Kleckner
2009-07-28 20:20 ` Eli Zaretskii
2009-07-28 22:23 ` Reid Kleckner
2009-07-29 15:20 ` Eli Zaretskii
2009-07-24 21:06 ` Tom Tromey
2009-07-25 0:23 ` Reid Kleckner
2009-07-30 16:30 ` Tom Tromey
2009-07-30 16:54 ` Tom Tromey
2009-08-05 21:05 ` [unladen-swallow] " Reid Kleckner
2009-07-30 21:10 ` Thiago Jung Bauermann
2009-07-31 18:18 ` Thiago Jung Bauermann
2009-07-31 20:31 ` [unladen-swallow] " Reid Kleckner
2009-08-01 14:43 ` Thiago Jung Bauermann
2009-08-14 19:29 ` Tom Tromey
2009-08-14 23:37 ` Reid Kleckner
2009-08-17 15:31 ` Tom Tromey
2009-08-20 18:22 ` Doug Evans
2009-08-21 15:17 ` Ken Werner
2009-08-21 16:31 ` Doug Evans
2009-08-21 18:59 ` Ken Werner
2009-08-21 19:53 ` Doug Evans
2009-07-31 20:55 ` Paul Pluzhnikov [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=8ac60eac0907311245p39481427y4071e5eeef655c89@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=gdb-patches@sourceware.org \
--cc=rnk@mit.edu \
--cc=thiago.bauermann@gmail.com \
--cc=tromey@redhat.com \
--cc=unladen-swallow@googlegroups.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