Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/4] record: set stop_pc in "record goto" command
Date: Wed, 08 Jul 2015 13:42:00 -0000	[thread overview]
Message-ID: <559D28A4.3040402@redhat.com> (raw)
In-Reply-To: <1436360074-8625-2-git-send-email-markus.t.metzger@intel.com>

On 07/08/2015 01:54 PM, Markus Metzger wrote:

> 2015-07-08  Markus Metzger <markus.t.metzger@intel.com>
> 
> gdb/
> 	* record-btrace.c (record_btrace_goto_begin, record_btrace_goto_end)
> 	record_btrace_goto): Set stop_pc.  Call reinit_frame_cache.
> 	* record-full.c (record_full_goto_entry): Set stop_pc.
> 
> testsuite/
> 	* gdb.btrace/record_goto-step.exp: New.
> ---
>  gdb/record-btrace.c                           |  6 ++++
>  gdb/record-full.c                             |  1 +
>  gdb/testsuite/gdb.btrace/record_goto-step.exp | 46 +++++++++++++++++++++++++++
>  3 files changed, 53 insertions(+)
>  create mode 100644 gdb/testsuite/gdb.btrace/record_goto-step.exp
> 
> diff --git a/gdb/record-btrace.c b/gdb/record-btrace.c
> index 969e01b..3870400 100644
> --- a/gdb/record-btrace.c
> +++ b/gdb/record-btrace.c
> @@ -2227,6 +2227,8 @@ record_btrace_goto_begin (struct target_ops *self)
>    btrace_insn_begin (&begin, &tp->btrace);
>    record_btrace_set_replay (tp, &begin);
>  
> +  reinit_frame_cache ();
> +  stop_pc = regcache_read_pc (get_current_regcache ());

I think you should do this within record_btrace_set_replay,
instead of doing the same in several places.

Also, I don't think you need the reinit_frame_cache call, as the
registers_changed_ptid calls in
record_btrace_set_replay/record_btrace_stop_replaying take care of
it already.

Thanks,
Pedro Alves


  reply	other threads:[~2015-07-08 13:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 12:54 [PATCH 1/4] btrace: fix build fail with 32-bit BFD Markus Metzger
2015-07-08 12:54 ` [PATCH 2/4] record: set stop_pc in "record goto" command Markus Metzger
2015-07-08 13:42   ` Pedro Alves [this message]
2015-07-08 15:08     ` Metzger, Markus T
2015-07-08 15:11       ` Pedro Alves
2015-07-08 12:54 ` [PATCH 3/4] ari, btrace: avoid unsigned long long Markus Metzger
2015-07-08 13:40   ` Pedro Alves
2015-07-08 14:05     ` Metzger, Markus T
2015-07-08 12:54 ` [PATCH 4/4] btrace, pt: support new packets Markus Metzger
2015-07-08 13:45   ` Pedro Alves
2015-07-08 13:42 ` [PATCH 1/4] btrace: fix build fail with 32-bit BFD Pedro Alves
2015-07-13  7:39   ` Metzger, Markus T
2015-07-13  9:39     ` 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=559D28A4.3040402@redhat.com \
    --to=palves@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