From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: [testsuite] kfail sigaltstack.exp on i386/gnu/linux
Date: Sun, 08 Aug 2004 22:02:00 -0000 [thread overview]
Message-ID: <20040808220220.GA22738@nevyn.them.org> (raw)
See PR 1736 and the link to gdb@ for more information. I've kfailed
this bug because, while the bug is external, GDB could handle it more
gracefully...
Tested on i686-pc-linux-gnu, where six of the tests FAIL->KFAIL. OK?
--
Daniel Jacobowitz
2004-08-08 Daniel Jacobowitz <dan@debian.org>
PR gdb/1736
* gdb.base/sigaltstack.exp (finish_test): New procedure. KFAIL
for i?86-*-linux*.
Index: testsuite/gdb.base/sigaltstack.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/sigaltstack.exp,v
retrieving revision 1.1
diff -u -p -r1.1 sigaltstack.exp
--- testsuite/gdb.base/sigaltstack.exp 5 Apr 2004 21:00:21 -0000 1.1
+++ testsuite/gdb.base/sigaltstack.exp 8 Aug 2004 22:00:02 -0000
@@ -78,11 +78,26 @@ gdb_expect_list "backtrace" ".*$gdb_prom
"\[\r\n\]+.7 \[^\r\n\]* main .*"
}
+proc finish_test { pattern msg } {
+ gdb_test_multiple "finish" $msg {
+ -re "Cannot insert breakpoint 0" {
+ # Some platforms use a special read-only page for signal
+ # trampolines. We can't set a breakpoint there, and we
+ # don't gracefully fall back to single-stepping.
+ setup_kfail "i?86-*-linux*" gdb/1736
+ fail "$msg (could not set breakpoint)"
+ }
+ -re "$pattern" {
+ pass $msg
+ }
+ }
+}
+
# Finish?
-gdb_test "finish" "signal handler called." "finish from catch LEAF"
-gdb_test "finish" "thrower .next_level=INNER, .*" "finish to throw INNER"
-gdb_test "finish" "catcher .*" "finish to catch INNER"
-gdb_test "finish" "signal handler called.*" "finish from catch INNER"
-gdb_test "finish" "thrower .next_level=OUTER, .*" "finish to OUTER"
-gdb_test "finish" "catcher .*" "finish to catch MAIN"
-gdb_test "finish" "main .*" "finish to MAIN"
+finish_test "signal handler called." "finish from catch LEAF"
+finish_test "thrower .next_level=INNER, .*" "finish to throw INNER"
+finish_test "catcher .*" "finish to catch INNER"
+finish_test "signal handler called.*" "finish from catch INNER"
+finish_test "thrower .next_level=OUTER, .*" "finish to OUTER"
+finish_test "catcher .*" "finish to catch MAIN"
+finish_test "main .*" "finish to MAIN"
next reply other threads:[~2004-08-08 22:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-08 22:02 Daniel Jacobowitz [this message]
2004-08-08 22:22 ` Michael Chastain
2004-08-08 23:14 ` Daniel Jacobowitz
2004-08-09 6:59 ` Michael Chastain
2004-08-09 17:15 ` Mark Kettenis
2004-08-09 17:30 ` Daniel Jacobowitz
2004-08-09 18:50 ` Michael Chastain
2004-08-09 17:27 ` Mark Kettenis
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=20040808220220.GA22738@nevyn.them.org \
--to=drow@false.org \
--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