From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Cc: Yichao Yu <yyc1992@gmail.com>
Subject: Re: [PATCH 0/3] Fix PR gdb/19858: GDB doesn't register the JIT libraries on attach
Date: Thu, 31 Mar 2016 18:47:00 -0000 [thread overview]
Message-ID: <56FD70A8.6090503@redhat.com> (raw)
In-Reply-To: <1458739792-9864-1-git-send-email-palves@redhat.com>
On 03/23/2016 01:29 PM, Pedro Alves wrote:
> As discussed at https://sourceware.org/ml/gdb/2016-03/msg00023.html,
> GDB currently fails to fetch the list of already-registered JIT
> modules on attach. This series fixes gdb, and adds a regression test.
>
> I'm aiming at pushing it to both master and the 7.11 branch.
Now pushed, both master and 7.11 branch.
Thanks,
Pedro Alves
> Tested on x86_64 Fedora 23.
>
> Pedro Alves (2):
> Make gdb.base/jit.exp binaries unique
> Add regression test for PR gdb/19858 (JIT code registration on attach)
>
> Yichao Yu (1):
> Fix PR gdb/19858: GDB doesn't register the JIT libraries on attach
>
> gdb/jit.c | 13 +++++-
> gdb/testsuite/gdb.base/jit-main.c | 21 +++++++++-
> gdb/testsuite/gdb.base/jit.exp | 88 +++++++++++++++++++++++++++++++--------
> 3 files changed, 101 insertions(+), 21 deletions(-)
>
prev parent reply other threads:[~2016-03-31 18:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 13:30 Pedro Alves
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
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-31 18:47 ` Pedro Alves [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=56FD70A8.6090503@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--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).