From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch v4 13/24] record-btrace, frame: supply target-specific unwinder
Date: Sun, 18 Aug 2013 19:07:00 -0000 [thread overview]
Message-ID: <20130818190742.GJ24153@host2.jankratochvil.net> (raw)
In-Reply-To: <1372842874-28951-14-git-send-email-markus.t.metzger@intel.com>
On Wed, 03 Jul 2013 11:14:23 +0200, Markus Metzger wrote:
> Supply a target-specific frame unwinder for the record-btrace target that does
> not allow unwinding while replaying.
>
> 2013-02-11 Jan Kratochvil <jan.kratochvil@redhat.com>
> Markus Metzger <markus.t.metzger@intel.com>
>
> gdb/
> * record-btrace.c: Include frame-unwind.h.
> (record_btrace_frame_unwind_stop_reason,
> record_btrace_frame_this_id, record_btrace_frame_prev_register,
> record_btrace_frame_sniffer, record_btrace_frame_unwind):
> New.
> (init_record_btrace_ops): Install it.
>
>
> ---
> gdb/record-btrace.c | 66 +++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 66 insertions(+), 0 deletions(-)
>
> diff --git a/gdb/record-btrace.c b/gdb/record-btrace.c
> index e9c0801..cb1f3bb 100644
> --- a/gdb/record-btrace.c
> +++ b/gdb/record-btrace.c
> @@ -33,6 +33,7 @@
> #include "symtab.h"
> #include "filenames.h"
> #include "regcache.h"
> +#include "frame-unwind.h"
>
> /* The target_ops of record-btrace. */
> static struct target_ops record_btrace_ops;
> @@ -844,6 +845,70 @@ record_btrace_prepare_to_store (struct target_ops *ops,
> }
> }
>
> +/* Implement stop_reason method for record_btrace_frame_unwind. */
> +
> +static enum unwind_stop_reason
> +record_btrace_frame_unwind_stop_reason (struct frame_info *this_frame,
> + void **this_cache)
> +{
> + return UNWIND_UNAVAILABLE;
> +}
> +
> +/* Implement this_id method for record_btrace_frame_unwind. */
> +
> +static void
> +record_btrace_frame_this_id (struct frame_info *this_frame, void **this_cache,
> + struct frame_id *this_id)
> +{
> + /* Leave there the outer_frame_id value. */
> +}
> +
> +/* Implement prev_register method for record_btrace_frame_unwind. */
> +
> +static struct value *
> +record_btrace_frame_prev_register (struct frame_info *this_frame,
> + void **this_cache,
> + int regnum)
> +{
> + throw_error (NOT_AVAILABLE_ERROR,
> + _("Registers are not available in btrace record history"));
> +}
> +
> +/* Implement sniffer method for record_btrace_frame_unwind. */
> +
> +static int
> +record_btrace_frame_sniffer (const struct frame_unwind *self,
> + struct frame_info *this_frame,
> + void **this_cache)
> +{
> + struct thread_info *tp;
> + struct btrace_thread_info *btinfo;
> + struct btrace_insn_iterator *replay;
> +
> + /* This doesn't seem right. Yet, I don't see how I could get from a frame
> + to its thread. */
That's OK. Either remove the comment or:
/* THIS_FRAME does not contain a reference to its thread. */
> + tp = find_thread_ptid (inferior_ptid);
> + if (tp == NULL)
> + return 0;
gdb_assert (tp != NULL);
> +
> + return btrace_is_replaying (tp);
> +}
> +
> +/* btrace recording does not store previous memory content, neither the stack
> + frames content. Any unwinding would return errorneous results as the stack
> + contents no longer matches the changed PC value restored from history.
> + Therefore this unwinder reports any possibly unwound registers as
> + <unavailable>. */
> +
> +static const struct frame_unwind record_btrace_frame_unwind =
> +{
> + NORMAL_FRAME,
> + record_btrace_frame_unwind_stop_reason,
> + record_btrace_frame_this_id,
> + record_btrace_frame_prev_register,
> + NULL,
> + record_btrace_frame_sniffer
> +};
> /* Initialize the record-btrace target ops. */
>
> static void
> @@ -874,6 +939,7 @@ init_record_btrace_ops (void)
> ops->to_fetch_registers = record_btrace_fetch_registers;
> ops->to_store_registers = record_btrace_store_registers;
> ops->to_prepare_to_store = record_btrace_prepare_to_store;
> + ops->to_get_unwinder = &record_btrace_frame_unwind;
> ops->to_stratum = record_stratum;
> ops->to_magic = OPS_MAGIC;
> }
> --
> 1.7.1
next prev parent reply other threads:[~2013-08-18 19:07 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 9:15 [patch v4 00/24] record-btrace: reverse Markus Metzger
2013-07-03 9:14 ` [patch v4 10/24] target: add ops parameter to to_prepare_to_store method Markus Metzger
2013-08-18 19:07 ` Jan Kratochvil
2013-07-03 9:14 ` [patch v4 03/24] btrace: change branch trace data structure Markus Metzger
2013-08-18 19:05 ` Jan Kratochvil
2013-09-10 9:11 ` Metzger, Markus T
2013-09-12 20:09 ` Jan Kratochvil
2013-09-16 9:01 ` Metzger, Markus T
2013-09-21 19:44 ` Jan Kratochvil
2013-09-23 6:54 ` Metzger, Markus T
2013-09-23 7:15 ` Jan Kratochvil
2013-09-23 7:27 ` Metzger, Markus T
2013-09-22 16:57 ` Jan Kratochvil
2013-09-22 17:16 ` Jan Kratochvil
2013-07-03 9:14 ` [patch v4 19/24] btrace, linux: fix memory leak when reading branch trace Markus Metzger
2013-08-18 19:09 ` Jan Kratochvil
2013-07-03 9:14 ` [patch v4 11/24] record-btrace: supply register target methods Markus Metzger
2013-08-18 19:07 ` Jan Kratochvil
2013-09-16 9:19 ` Metzger, Markus T
2013-09-22 13:55 ` Jan Kratochvil
2013-09-23 6:55 ` Metzger, Markus T
2013-07-03 9:14 ` [patch v4 20/24] btrace, gdbserver: read branch trace incrementally Markus Metzger
2013-08-18 19:09 ` Jan Kratochvil
2013-09-16 12:48 ` Metzger, Markus T
2013-09-22 14:42 ` Jan Kratochvil
2013-09-23 7:09 ` Metzger, Markus T
2013-09-25 19:05 ` Jan Kratochvil
2013-09-26 6:27 ` Metzger, Markus T
2013-07-03 9:14 ` [patch v4 24/24] record-btrace: skip tail calls in back trace Markus Metzger
2013-08-18 19:10 ` Jan Kratochvil
2013-09-17 14:28 ` Metzger, Markus T
2013-09-18 8:28 ` Metzger, Markus T
2013-09-18 9:52 ` Metzger, Markus T
2013-07-03 9:14 ` [patch v4 22/24] infrun: reverse stepping from unknown functions Markus Metzger
2013-08-18 19:09 ` Jan Kratochvil
2013-07-03 9:14 ` [patch v4 07/24] record-btrace: optionally indent function call history Markus Metzger
2013-08-18 19:06 ` Jan Kratochvil
2013-09-10 13:06 ` Metzger, Markus T
2013-09-10 13:08 ` Jan Kratochvil
2013-07-03 9:14 ` [patch v4 08/24] record-btrace: make ranges include begin and end Markus Metzger
2013-08-18 19:12 ` Jan Kratochvil
2013-07-03 9:14 ` [patch v4 16/24] record-btrace: provide target_find_new_threads method Markus Metzger
2013-08-18 19:15 ` Jan Kratochvil
2013-07-03 9:14 ` [patch v4 02/24] record: upcase record_print_flag enumeration constants Markus Metzger
2013-08-18 19:11 ` Jan Kratochvil
2013-07-03 9:14 ` [patch v4 14/24] record-btrace: provide xfer_partial target method Markus Metzger
2013-08-18 19:08 ` Jan Kratochvil
2013-09-16 9:30 ` Metzger, Markus T
2013-09-22 14:18 ` Jan Kratochvil
2013-07-03 9:14 ` [patch v4 09/24] btrace: add replay position to btrace thread info Markus Metzger
2013-08-18 19:07 ` Jan Kratochvil
2013-09-10 13:24 ` Metzger, Markus T
2013-09-12 20:19 ` Jan Kratochvil
2013-07-03 9:14 ` [patch v4 05/24] record-btrace: start counting at one Markus Metzger
2013-08-18 19:11 ` Jan Kratochvil
2013-07-03 9:15 ` [patch v4 12/24] frame, backtrace: allow targets to supply a frame unwinder Markus Metzger
2013-08-18 19:14 ` Jan Kratochvil
2013-07-03 9:15 ` [patch v4 18/24] record-btrace: extend unwinder Markus Metzger
2013-08-18 19:08 ` Jan Kratochvil
2013-09-16 11:21 ` Metzger, Markus T
2013-09-27 13:55 ` Jan Kratochvil
2013-09-30 9:45 ` Metzger, Markus T
2013-09-30 10:26 ` Jan Kratochvil
2013-07-03 9:15 ` [patch v4 21/24] record-btrace: show trace from enable location Markus Metzger
2013-08-18 19:10 ` instruction_history.exp unset variable [Re: [patch v4 21/24] record-btrace: show trace from enable location] Jan Kratochvil
2013-09-16 14:11 ` Metzger, Markus T
2013-08-18 19:16 ` [patch v4 21/24] record-btrace: show trace from enable location Jan Kratochvil
2013-07-03 9:15 ` [patch v4 04/24] record-btrace: fix insn range in function call history Markus Metzger
2013-08-18 19:06 ` Jan Kratochvil
2013-07-03 9:15 ` [patch v4 01/24] gdbarch: add instruction predicate methods Markus Metzger
2013-07-03 9:49 ` Mark Kettenis
2013-07-03 11:10 ` Metzger, Markus T
2013-08-18 19:04 ` Jan Kratochvil
2013-07-03 9:15 ` [patch v4 23/24] record-btrace: add (reverse-)stepping support Markus Metzger
2013-08-18 19:09 ` Jan Kratochvil
2013-09-17 9:43 ` Metzger, Markus T
2013-09-29 17:24 ` Jan Kratochvil
2013-09-30 9:30 ` Metzger, Markus T
2013-09-30 10:25 ` Jan Kratochvil
2013-07-03 9:15 ` [patch v4 06/24] btrace: increase buffer size Markus Metzger
2013-08-18 19:06 ` Jan Kratochvil
2013-07-03 9:15 ` [patch v4 17/24] record-btrace: add record goto target methods Markus Metzger
2013-08-18 19:08 ` Jan Kratochvil
2013-07-03 9:15 ` [patch v4 15/24] record-btrace: add to_wait and to_resume " Markus Metzger
2013-08-18 19:08 ` Jan Kratochvil
2013-07-03 9:15 ` [patch v4 13/24] record-btrace, frame: supply target-specific unwinder Markus Metzger
2013-08-18 19:07 ` Jan Kratochvil [this message]
2013-08-18 19:04 ` [patch v4 00/24] record-btrace: reverse Jan Kratochvil
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=20130818190742.GJ24153@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.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