Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	  teawater <teawater@gmail.com>
Subject: Re: [reverse/record] adjust_pc_after_break in reverse execution mode?
Date: Fri, 24 Oct 2008 00:45:00 -0000	[thread overview]
Message-ID: <49011935.5080604@vmware.com> (raw)
In-Reply-To: <200810240054.31546.pedro@codesourcery.com>

Thank you!
I'll put it on the branch for now...

Does it make sense to include a forward version of this test,
for normal (non-reverse/non-replay) targets?

Pedro Alves wrote:
>> I've done so a bit this morning, and came to a similar
>> conclusion, although I noticed Hui's change to set stop_pc in
>> TARGET_WAITKIND_NO_HISTORY, also also required.  I was wanting
>> to find time to play a little bit more, but since you're on to it...
> 
> BTW, I noticed that, while reviewing Hui's latest patch
> (which was missing setting the waitkind to TARGET_WAITKIND_STOPPED,
> hence could never work :-) ).  While doing so, I dejagnufied the
> nop testcase into the attached.  Maybe you'll find it useful.
> 
> --
> Pedro Alves
> 
> 
> ------------------------------------------------------------------------
> 
> 2008-10-24  Pedro Alves  <pedro@codesourcery.com>
> 
> 	* gdb.base/decr-pc-rev.c, gdb.base/decr-pc-rev.exp: New test.
> 
> ---
>  gdb/testsuite/gdb.base/decr-pc-rev.c   |   26 +++++++++
>  gdb/testsuite/gdb.base/decr-pc-rev.exp |   86 +++++++++++++++++++++++++++++++++
>  2 files changed, 112 insertions(+)
> 
> Index: src/gdb/testsuite/gdb.base/decr-pc-rev.c
> ===================================================================
> --- /dev/null	1970-01-01 00:00:00.000000000 +0000
> +++ src/gdb/testsuite/gdb.base/decr-pc-rev.c	2008-10-23 15:21:02.000000000 +0100
> @@ -0,0 +1,26 @@
> +/* This testcase is part of GDB, the GNU debugger.
> +
> +   Copyright 2008 Free Software Foundation, Inc.
> +
> +   This program is free software; you can redistribute it and/or modify
> +   it under the terms of the GNU General Public License as published by
> +   the Free Software Foundation; either version 3 of the License, or
> +   (at your option) any later version.
> +
> +   This program is distributed in the hope that it will be useful,
> +   but WITHOUT ANY WARRANTY; without even the implied warranty of
> +   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> +   GNU General Public License for more details.
> +
> +   You should have received a copy of the GNU General Public License
> +   along with this program.  If not, see <http://www.gnu.org/licenses/>.  */
> +
> +int
> +main ()
> +{
> +  asm ("nop"); /* first insn */
> +  asm ("nop"); /* second insn */
> +  asm ("nop"); /* third insn */
> +  asm ("nop"); /* fourth insn */
> +  return 0;
> +}
> Index: src/gdb/testsuite/gdb.base/decr-pc-rev.exp
> ===================================================================
> --- /dev/null	1970-01-01 00:00:00.000000000 +0000
> +++ src/gdb/testsuite/gdb.base/decr-pc-rev.exp	2008-10-23 15:21:02.000000000 +0100
> @@ -0,0 +1,86 @@
> +#   Copyright 2008 Free Software Foundation, Inc.
> +
> +# This program is free software; you can redistribute it and/or modify
> +# it under the terms of the GNU General Public License as published by
> +# the Free Software Foundation; either version 3 of the License, or
> +# (at your option) any later version.
> +#
> +# This program is distributed in the hope that it will be useful,
> +# but WITHOUT ANY WARRANTY; without even the implied warranty of
> +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> +# GNU General Public License for more details.
> +#
> +# You should have received a copy of the GNU General Public License
> +# along with this program.  If not, see <http://www.gnu.org/licenses/>.
> +
> +if $tracelevel then {
> +    strace $tracelevel
> +}
> +
> +# Test PC adjustment behaviour on decr_pc_after_break archs in reverse
> +# and replay modes, in the presence of breakpoints at consecutive
> +# instruction addresses.
> +
> +set testfile "decr-pc-rev"
> +set srcfile ${testfile}.c
> +set binfile ${objdir}/${subdir}/${testfile}
> +
> +if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug nowarnings}] != "" } {
> +    untested consecutive.exp
> +    return -1
> +}
> +
> +if [get_compiler_info ${binfile}] {
> +    return -1
> +}
> +
> +gdb_exit
> +gdb_start
> +gdb_reinitialize_dir $srcdir/$subdir
> +gdb_load ${binfile}
> +
> +if [target_info exists gdb_stub] {
> +    gdb_step_for_stub;
> +}
> +
> +if ![runto_main] then {
> +    perror "couldn't run to breakpoint"
> +    continue
> +}
> +
> +# These breakpoint should be placed at consecutive instructions, such
> +# that the address difference between them is equal to
> +# decr_pc_after_break on this arquitecture.
> +
> +set bp_location1 [gdb_get_line_number "first insn"]
> +set bp_location2 [gdb_get_line_number "second insn"]
> +
> +# Enable recording.
> +
> +gdb_test "record" "" "enable record target"
> +
> +# Step through the breakpoints creating some history.
> +
> +gdb_test "next" ".*second insn.*" "next (1)"
> +gdb_test "next" ".*third insn.*" "next (2)"
> +gdb_test "next" ".*fourth insn.*" "next (3)"
> +gdb_test "next" ".*return 0.*" "next (4)"
> +
> +# Set consecutive breakpoints.
> +
> +gdb_test "break $bp_location1" \
> +    ".*Breakpoint .*$srcfile, line $bp_location1\\." \
> +    "first breakpoint line number"
> +
> +gdb_test "break $bp_location2" \
> +    "Breakpoint.*at.* file .*$srcfile, line $bp_location2\\." \
> +    "second breakpoint line number"
> +
> +# Test that reverse-continue doesn't mess with decr_pc_after_break
> +
> +gdb_test "rc" ".*second insn.*" "reverse continue to breakpoint"
> +gdb_test "rn" ".*first insn.*" "reverse next to begining of times"
> +
> +# Test that replay behaves as normal play.
> +gdb_test "next" ".*second insn.*" "next (1) in replay"
> +gdb_test "next" ".*third insn.*" "next (2) in replay"


  reply	other threads:[~2008-10-24  0:45 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-18  1:11 Pedro Alves
2008-10-18  1:26 ` Michael Snyder
2008-10-18  3:09   ` Pedro Alves
2008-10-18  3:18     ` teawater
2008-10-18  8:42     ` Andreas Schwab
2008-10-19 14:28       ` teawater
2008-10-19 20:10     ` Daniel Jacobowitz
2008-10-18  3:07 ` teawater
2008-10-18  3:26   ` Pedro Alves
2008-10-19 22:44 ` Michael Snyder
2008-10-20  0:10   ` Pedro Alves
2008-10-20  0:44     ` Michael Snyder
2008-10-20  1:46       ` Daniel Jacobowitz
2008-10-20 12:10       ` Pedro Alves
2008-10-20 15:50         ` teawater
2008-10-20 17:44       ` Pedro Alves
2008-10-20 17:51         ` Michael Snyder
2008-10-20 23:36           ` teawater
2008-10-21  0:21             ` Pedro Alves
2008-10-21  0:56               ` teawater
2008-10-21  3:13                 ` teawater
2008-10-21  6:52               ` teawater
2008-10-21  6:52                 ` teawater
2008-10-23 23:28                 ` Michael Snyder
2008-10-21  7:04               ` teawater
2008-10-21 18:36                 ` Michael Snyder
2008-10-22  0:39                   ` teawater
2008-10-23 23:32     ` Michael Snyder
2008-10-23 23:46       ` Pedro Alves
2008-10-23 23:55         ` Pedro Alves
2008-10-24  0:45           ` Michael Snyder [this message]
2008-10-24  0:43         ` Michael Snyder
2008-10-24  1:51           ` Pedro Alves
2008-10-24  8:11             ` teawater
2008-10-24  9:58               ` teawater
2008-10-25  7:08                 ` teawater
2008-10-28  3:21                   ` teawater
2008-10-29  1:24                   ` Michael Snyder
2008-10-30  3:01                     ` teawater
2008-10-30 12:21                     ` Pedro Alves
2008-10-30 22:06                       ` Michael Snyder
2008-10-30 21:44                         ` Pedro Alves
2008-10-30 21:29                           ` Michael Snyder
2008-10-31 13:04                           ` teawater
2008-10-31  0:25                       ` teawater

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=49011935.5080604@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=teawater@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