From: Pedro Alves <palves@redhat.com>
To: Yichao Yu <yyc1992@gmail.com>,
gdb@sourceware.org,
Paul Pluzhnikov <ppluzhnikov@google.com>
Subject: Re: JIT debugging (Attach and speed)
Date: Tue, 22 Mar 2016 16:15:00 -0000 [thread overview]
Message-ID: <56F16F8F.9050404@redhat.com> (raw)
In-Reply-To: <56F168D7.9050405@redhat.com>
On 03/22/2016 03:46 PM, Pedro Alves wrote:
>> 2. JIT code registration on attach is broken.
>>
>> When I set a breakpoint on `jit_inferior_init`[3] (i.e. lauching
>> gdb with `gdb --args gdb -p <pid_to_debug>`) which IIUC is what
>> responsible for walking the jit object list at init time, it seems
>> that the function is never called.
>>
>> (I haven't seen a bug report about this yet)
>
> Do you know whether this happens with 7.11 and master, and if so,
> would it be possible for you to git bisect the culprit?
Currently, jit_inferior_created_hook -> jit_inferior_init is only
called when the inferior execs...
Grepping around, I think that might have been
the fix for PR gdb/13431 (03bef283c2d3):
https://sourceware.org/ml/gdb-patches/2012-02/msg00023.html
which removed the inferior_created (jit_inferior_created_observer).
Adding an inferior_created observer back likely fixes the issue.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-03-22 16:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 14:56 Yichao Yu
2016-03-22 15:46 ` Pedro Alves
2016-03-22 16:10 ` Paul Pluzhnikov
2016-03-22 16:15 ` Pedro Alves [this message]
2016-03-22 16:23 ` Yichao Yu
2016-03-22 16:41 ` Pedro Alves
2016-03-22 16:47 ` Yichao Yu
2016-03-22 17:00 ` Pedro Alves
2016-03-23 2:18 ` Yichao Yu
2016-03-23 4:51 ` Yichao Yu
2016-03-23 18:24 ` Pedro Alves
2016-03-23 19:32 ` Yichao Yu
2016-03-23 19:48 ` Pedro Alves
2016-03-23 20:51 ` Yichao Yu
2016-03-24 1:17 ` Pedro Alves
2016-03-24 3:14 ` Yichao Yu
2016-03-24 21:02 ` Yichao Yu
2016-03-23 12:24 ` Pedro Alves
2016-03-23 13:31 ` Pedro Alves
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=56F16F8F.9050404@redhat.com \
--to=palves@redhat.com \
--cc=gdb@sourceware.org \
--cc=ppluzhnikov@google.com \
--cc=yyc1992@gmail.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