public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org,  Yichao Yu <yyc1992@gmail.com>
Subject: Re: [PATCH 1/3] Fix PR gdb/19858: GDB doesn't register the JIT libraries on attach
Date: Thu, 24 Mar 2016 08:59:00 -0000	[thread overview]
Message-ID: <86h9fwtfnq.fsf@gmail.com> (raw)
In-Reply-To: <1458739792-9864-2-git-send-email-palves@redhat.com> (Pedro	Alves's message of "Wed, 23 Mar 2016 13:29:50 +0000")

Pedro Alves <palves@redhat.com> writes:

> gdb/ChangeLog:
> 2016-03-23  Yichao Yu  <yyc1992@gmail.com>
>
> 	PR gdb/19858
> 	* jit.c (jit_breakpoint_re_set_internal): Return 0 if we already
> 	got the breakpoint at the right address.
> 	(jit_inferior_created): New function.
> 	(_initialize_jit): Install jit_inferior_created as
> 	inferior_created observer.

Patch is good to me.

-- 
Yao (齐尧)

  reply	other threads:[~2016-03-24  8:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23 13:30 [PATCH 0/3] " Pedro Alves
2016-03-23 13:30 ` [PATCH 2/3] Make gdb.base/jit.exp binaries unique Pedro Alves
2016-03-24  9:01   ` Yao Qi
2016-09-27 17:46   ` [testsuite bugreport] gdb.base/jit.exp has false PASSes, probably [Re: [PATCH 2/3] Make gdb.base/jit.exp binaries unique] Jan Kratochvil
2016-03-23 13:30 ` [PATCH 3/3] Add regression test for PR gdb/19858 (JIT code registration on attach) Pedro Alves
2016-03-24  9:15   ` Yao Qi
2016-03-23 13:30 ` [PATCH 1/3] Fix PR gdb/19858: GDB doesn't register the JIT libraries on attach Pedro Alves
2016-03-24  8:59   ` Yao Qi [this message]
2016-03-31 18:47 ` [PATCH 0/3] " 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=86h9fwtfnq.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).