From: Corinna Vinschen <vinschen@redhat.com>
To: gdb-patches <gdb-patches@sources.redhat.com>
Subject: [PATCH]: (obvious) testsuite/gdb.base/ending-run.exp
Date: Mon, 29 Oct 2001 10:17:00 -0000 [thread overview]
Message-ID: <20011029191707.N891@cygbert.vinschen.de> (raw)
Hi,
I just applied the following patch according to the "obvious fix rule"
to gdb.base/ending-run.exp. It makes the output of the pass branches
in the `step to end of run' case equal and adds a branch for the
Stormy16 target.
Corinna
2001-10-29 Corinna Vinschen <vinschen@redhat.com>
* gdb.base/ending-run.exp: Create identical output when passing
`step to end of run' case. Add regular expression branch satisfying
Stormy16 target.
Index: testsuite/gdb.base/ending-run.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/ending-run.exp,v
retrieving revision 1.8
diff -u -p -r1.8 ending-run.exp
--- ending-run.exp 2001/09/18 17:49:06 1.8
+++ ending-run.exp 2001/10/29 18:12:41
@@ -219,14 +219,18 @@ if {![target_info exists use_cygmon] ||
# If we actually have debug info for the start function,
# then we won't get the "Single-stepping until function
# exit" message.
- pass "step to end of run 1"
+ pass "step to end of run"
}
-re ".*Single.*Program exited.*$gdb_prompt $" {
- pass "step to end of run 1"
+ pass "step to end of run"
}
-re ".*Single.*in exit.*from.*dld.sl.*$gdb_prompt $" {
- pass "step to end of run 2"
+ pass "step to end of run"
gdb_test "c" ".*" "continue after exit"
+ }
+ -re ".*Single.*_int_reset.*$gdb_prompt $" {
+ pass "step to end of run"
+ setup_xfail "stormy16-*-*"
}
-re ".*$gdb_prompt $" {
fail "step to end of run"
next reply other threads:[~2001-10-29 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 10:17 Corinna Vinschen [this message]
2001-10-29 10:22 ` Fernando Nasser
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=20011029191707.N891@cygbert.vinschen.de \
--to=vinschen@redhat.com \
--cc=gdb-patches@sources.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