Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] fix for step-reverse.exp
Date: Thu, 16 Jul 2009 07:45:00 -0000	[thread overview]
Message-ID: <daef60380907151941r4491b66k6ba8e5553cd48a4f@mail.gmail.com> (raw)
In-Reply-To: <4A5CE7DB.5090501@vmware.com>

On Wed, Jul 15, 2009 at 04:17, Michael Snyder<msnyder@vmware.com> wrote:
> Hui's amd64 patch was failing this test, because the test
> neglects to allow for the possibility that the call instruction
> is not the first instruction on the line.
>
> Hui, try it now.
>

It works very cool. Thanks.  :)

Hui


>
> 2009-07-14  Michael Snyder  <msnyder@vmware.com>
>
>        * gdb.reverse/step-reverse.exp (stepi into function call):
>        Call instruction may not be first instruction in the line.
>        (reverse stepi from a function call): Used wrong line number.
>
> Index: gdb.reverse/step-reverse.exp
> ===================================================================
> RCS file: /cvs/src/src/gdb/testsuite/gdb.reverse/step-reverse.exp,v
> retrieving revision 1.1
> diff -u -p -r1.1 step-reverse.exp
> --- gdb.reverse/step-reverse.exp        27 Jun 2009 18:49:20 -0000      1.1
> +++ gdb.reverse/step-reverse.exp        14 Jul 2009 20:16:42 -0000
> @@ -104,6 +104,10 @@ gdb_test_multiple "stepi" "$test_message
>        send_gdb "stepi\n"
>        exp_continue
>     }
> +    -re "STEPI TEST.*$gdb_prompt $" {
> +       send_gdb "stepi\n"
> +       exp_continue
> +    }
>  }
>
>  # stepi thru return of a function call
> @@ -168,7 +172,7 @@ gdb_test_multiple "stepi" "$test_message
>
>  # stepi backward out of a function call
>
> -set stepi_location  [gdb_get_line_number "FINISH TEST" "$srcfile"]
> +set stepi_location  [gdb_get_line_number "STEPI TEST" "$srcfile"]
>  set test_message "reverse stepi from a function call"
>  gdb_test_multiple "stepi" "$test_message" {
>     -re "ARRIVED IN CALLEE.*$gdb_prompt $" {
> @@ -178,7 +182,7 @@ gdb_test_multiple "stepi" "$test_message
>        send_gdb "stepi\n"
>        exp_continue
>     }
> -    -re "${hex}\[ \t\]*$stepi_location.*STEPI TEST.*$gdb_prompt $" {
> +    -re "${hex} in main .*:$stepi_location.*STEPI TEST.*$gdb_prompt $" {
>        send_gdb "stepi\n"
>        exp_continue
>     }
>
>


      reply	other threads:[~2009-07-16  2:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14 22:55 Michael Snyder
2009-07-16  7:45 ` Hui Zhu [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=daef60380907151941r4491b66k6ba8e5553cd48a4f@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.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