From: Anton Blanchard <anton@samba.org>
To: gdb-patches@sourceware.org, brobecker@adacore.com,
emachado@linux.vnet.ibm.com, luis_gustavo@mentor.com,
ulrich.weigand@de.ibm.com, palves@redhat.com
Subject: [PATCH 3/3] gdb.arch/ppc64-atomic-inst.exp: Improve error handling.
Date: Mon, 31 Mar 2014 02:59:00 -0000 [thread overview]
Message-ID: <1396234730-12149-3-git-send-email-anton@samba.org> (raw)
In-Reply-To: <1396234730-12149-1-git-send-email-anton@samba.org>
gdb/testsuite/
2014-03-31 Anton Blanchard <anton@samba.org>
* gdb.arch/ppc64-atomic-inst.exp: Use untested. Make test
messages unique.
---
gdb/testsuite/gdb.arch/ppc64-atomic-inst.exp | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/gdb/testsuite/gdb.arch/ppc64-atomic-inst.exp b/gdb/testsuite/gdb.arch/ppc64-atomic-inst.exp
index fc7568c..ff26697 100644
--- a/gdb/testsuite/gdb.arch/ppc64-atomic-inst.exp
+++ b/gdb/testsuite/gdb.arch/ppc64-atomic-inst.exp
@@ -33,26 +33,26 @@ if { [prepare_for_testing ${testfile}.exp ${testfile} ${srcfile} {debug quiet}]
}
if ![runto_main] then {
- perror "Couldn't run to breakpoint"
- continue
+ untested "could not run to main"
+ return -1
}
set bp1 [gdb_get_line_number "lwarx"]
gdb_breakpoint "$bp1" "Breakpoint $decimal at $hex" \
- "Set the breakpoint at the start of the sequence"
+ "Set the breakpoint at the start of the lwarx/stwcx sequence"
set bp2 [gdb_get_line_number "ldarx"]
gdb_breakpoint "$bp2" "Breakpoint $decimal at $hex" \
- "Set the breakpoint at the start of the sequence"
+ "Set the breakpoint at the start of the ldarx/stdcx sequence"
gdb_test continue "Continuing.*Breakpoint $decimal.*" \
- "Continue until breakpoint"
+ "Continue until lwarx/stwcx start breakpoint"
gdb_test nexti "bne.*1b" \
"Step through the lwarx/stwcx sequence"
gdb_test continue "Continuing.*Breakpoint $decimal.*" \
- "Continue until breakpoint"
+ "Continue until ldarx/stdcx start breakpoint"
gdb_test nexti "bne.*1b" \
- "Step through the lwarx/stwcx sequence"
+ "Step through the ldarx/stdcx sequence"
--
1.8.3.2
next prev parent reply other threads:[~2014-03-31 2:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 2:59 [PATCH 1/3] Fix ppc64 single step over atomic sequence testcase Anton Blanchard
2014-03-31 2:58 ` [PATCH 2/3] gdb.arch/ppc64-atomic-inst.exp: Use standard_testfile, prepare_for_testing Anton Blanchard
2014-03-31 15:39 ` Ulrich Weigand
2014-03-31 2:59 ` Anton Blanchard [this message]
2014-03-31 15:40 ` [PATCH 3/3] gdb.arch/ppc64-atomic-inst.exp: Improve error handling Ulrich Weigand
2014-03-31 15:38 ` [PATCH 1/3] Fix ppc64 single step over atomic sequence testcase Ulrich Weigand
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=1396234730-12149-3-git-send-email-anton@samba.org \
--to=anton@samba.org \
--cc=brobecker@adacore.com \
--cc=emachado@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=luis_gustavo@mentor.com \
--cc=palves@redhat.com \
--cc=ulrich.weigand@de.ibm.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