From: Elena Zannoni <ezannoni@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: Elena Zannoni <ezannoni@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA/MI testsuite] mi_run_to_main/mi_next/mi_step
Date: Tue, 10 Sep 2002 14:58:00 -0000 [thread overview]
Message-ID: <15742.27287.297281.525517@localhost.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0209100758280.1392-100000@valrhona.uglyboxes.com>
Keith Seitz writes:
> On Tue, 10 Sep 2002, Keith Seitz wrote:
>
> > This patch just fixes what is already in mi-support.exp, which doesn't
> > work at all. As an alternative, we could whack mi_step and mi_next (or I
> > we could even re-write those to use mi_step_to and mi_next_to, come to
> > think of it).
>
> Ok, here's the same patch but using mi_next_to and mi_step_to.
>
Yes. Thanks!
Elena
> Keith
>
> ChangeLog
> 2002-09-10 Keith Seitz <keiths@redhat.com>
>
> * lib/mi-support.exp: (mi_run_to_main): Allow anything to precede
> regexp for stopping at main. Could have multiple event notifications.
> Don't assume that main was declared with no parameters.
> (mi_next): Use mi_step_to.
> (mi_step): Use mi_next_to.
>
> Index: testsuite/lib/mi-support.exp
> ===================================================================
> RCS file: /cvs/src/src/gdb/testsuite/lib/mi-support.exp,v
> retrieving revision 1.15
> diff -p -r1.15 mi-support.exp
> *** testsuite/lib/mi-support.exp 4 Sep 2002 21:05:07 -0000 1.15
> --- testsuite/lib/mi-support.exp 10 Sep 2002 14:54:55 -0000
> *************** proc mi_run_to_main { } {
> *** 656,701 ****
>
>
> # Next to the next statement
>
> proc mi_next { test } {
> ! global suppress_flag
> ! if { $suppress_flag } {
> ! return -1
> ! }
> ! global mi_gdb_prompt
> ! send_gdb "220-exec-next\n"
> ! gdb_expect {
> ! -re "220\\^running\r\n${mi_gdb_prompt}220\\*stopped,reason=\"end-stepping-range\",thread-id=\"$decimal\",frame=\{addr=\"$hex\",func=\".*\",args=\[\\\[\{].*[\\\]\}\],file=\".*\",line=\"\[0-9\]*\"\}\r\n$mi_gdb_prompt$" {
> ! pass "$test"
> ! return 0
> ! }
> ! timeout {
> ! fail "$test"
> ! return -1
> ! }
> ! }
> }
>
>
> # Step to the next statement
>
> proc mi_step { test } {
> ! global suppress_flag
> ! if { $suppress_flag } {
> ! return -1
> ! }
> ! global mi_gdb_prompt
> ! send_gdb "220-exec-step\n"
> ! gdb_expect {
> ! -re "220\\^running\r\n${mi_gdb_prompt}220\\*stopped,reason=\"end-stepping-range\",thread-id=\"$decimal\",frame=\{addr=\"$hex\",func=\".*\",args=\[\\\[\{\].*\[\\\]\}\],file=\".*\",line=\"\[0-9\]*\"\}\r\n$mi_gdb_prompt$" {
> ! pass "$test"
> ! return 0
> ! }
> ! timeout {
> ! fail "$test"
> ! return -1
> ! }
> ! }
> }
>
> # cmd should not include the number or newline (i.e. "exec-step 3", not
> --- 656,673 ----
>
>
> # Next to the next statement
> + # For return values, see mi_run_to_helper
>
> proc mi_next { test } {
> ! return [mi_next_to {.*} {.*} {.*} {.*} $test]
> }
>
>
> # Step to the next statement
> + # For return values, see mi_run_to_helper
>
> proc mi_step { test } {
> ! return [mi_step_to {.*} {.*} {.*} {.*} $test]
> }
>
> # cmd should not include the number or newline (i.e. "exec-step 3", not
> *************** proc mi_run_to_helper { cmd reason func
> *** 714,724 ****
> global decimal
> send_gdb "220-$cmd\n"
> gdb_expect {
> ! -re "220\\^running\r\n${mi_gdb_prompt}220\\*stopped,reason=\"$reason\",thread-id=\"$decimal\",frame=\{addr=\"$hex\",func=\"$func\",args=$args,file=\".*$file\",line=\"$line\"\}$extra\r\n$mi_gdb_prompt$" {
> pass "$test"
> return 0
> }
> ! -re "220\\^running\r\n${mi_gdb_prompt}220\\*stopped,reason=\"$reason\",thread-id=\"$decimal\",frame=\{addr=\"$hex\",func=\".*\",args=\[\\\[\{\].*\[\\\]\}\],file=\".*\",line=\"\[0-9\]*\"\}.*\r\n$mi_gdb_prompt$" {
> fail "$test (stopped at wrong place)"
> return -1
> }
> --- 686,696 ----
> global decimal
> send_gdb "220-$cmd\n"
> gdb_expect {
> ! -re ".*220\\^running\r\n${mi_gdb_prompt}.*220\\*stopped,reason=\"$reason\",thread-id=\"$decimal\",frame=\{addr=\"$hex\",func=\"$func\",args=$args,file=\".*$file\",line=\"$line\"\}$extra\r\n$mi_gdb_prompt$" {
> pass "$test"
> return 0
> }
> ! -re ".*220\\^running\r\n${mi_gdb_prompt}.*220\\*stopped,reason=\"$reason\",thread-id=\"$decimal\",frame=\{addr=\"$hex\",func=\".*\",args=\[\\\[\{\].*\[\\\]\}\],file=\".*\",line=\"\[0-9\]*\"\}.*\r\n$mi_gdb_prompt$" {
> fail "$test (stopped at wrong place)"
> return -1
> }
next prev parent reply other threads:[~2002-09-10 21:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 13:43 Keith Seitz
2002-09-09 19:22 ` Elena Zannoni
2002-09-10 7:25 ` Keith Seitz
2002-09-10 9:32 ` Keith Seitz
2002-09-10 14:58 ` Elena Zannoni [this message]
2002-09-10 15:08 ` Keith Seitz
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=15742.27287.297281.525517@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=keiths@redhat.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