From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA 1/3] Clear frame cache when loading or unloading a JIT unwinder
Date: Fri, 17 Jun 2016 19:00:00 -0000 [thread overview]
Message-ID: <525d6968-595b-b4cf-f16e-83ac08f5559f@redhat.com> (raw)
In-Reply-To: <1465612923-24880-2-git-send-email-tom@tromey.com>
On 06/11/2016 03:42 AM, Tom Tromey wrote:
> It seemed to me that gdb should flush the frame cache when loading or
> unloading a JIT unwinder. This makes testing a JIT unwinder a bit
> simpler.
>
> jit-reader-load apparently has no tests in-tree, so I didn't add a new
> test here.
Yeah. Tests existed, but had never been pushed in the tree... I fixed
that now:
https://sourceware.org/ml/gdb-patches/2016-06/msg00308.html
Could you see if it's easy to extend the test to cover this?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-06-17 19:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 2:42 [RFA 0/3] unwinder registration and the frame cache Tom Tromey
2016-06-11 2:42 ` [RFA 2/3] Make gdbpy_parameter static Tom Tromey
2016-06-17 19:00 ` Pedro Alves
2016-06-24 2:46 ` Tom Tromey
2016-06-11 2:42 ` [RFA 3/3] PR python/19293 - invalidate frame cache when unwinders change Tom Tromey
2016-06-17 19:11 ` Pedro Alves
2016-06-24 2:55 ` Tom Tromey
2016-06-11 2:42 ` [RFA 1/3] Clear frame cache when loading or unloading a JIT unwinder Tom Tromey
2016-06-17 19:00 ` Pedro Alves [this message]
2016-06-24 2:40 ` Tom Tromey
2016-06-28 16:48 ` [PATCH] Extend JIT-reader test and fix GDB problems that exposes (was: Re: [RFA 1/3] Clear frame cache when loading or unloading a JIT unwinder) Pedro Alves
2016-06-28 22:14 ` [PATCH] Extend JIT-reader test and fix GDB problems that exposes Tom Tromey
2016-07-01 11:07 ` 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=525d6968-595b-b4cf-f16e-83ac08f5559f@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).