Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: dje@google.com (Doug Evans)
To: gdb-patches@sourceware.org
Subject: [RFA] kfail longjmp.exp tests due to bug 9270
Date: Thu, 18 Mar 2010 22:16:00 -0000	[thread overview]
Message-ID: <20100318221601.F233684413@ruffy.mtv.corp.google.com> (raw)

Anyone mind if I mark these as kfail for amd64?

2010-03-18  Doug Evans  <dje@google.com>

	* gdb.base/longjmp.exp: Mark tests that fail on x86_64 due to
	bug 9270 as kfail.

Index: longjmp.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/longjmp.exp,v
retrieving revision 1.4
diff -u -p -r1.4 longjmp.exp
--- longjmp.exp	1 Jan 2010 07:32:01 -0000	1.4
+++ longjmp.exp	18 Mar 2010 22:13:19 -0000
@@ -73,6 +73,7 @@ gdb_test "break $bp_miss_step_1" \
 gdb_test "next" "longjmps\\+\\+;.*" "next over setjmp (1)"
 gdb_test "next" "longjmp \\(env, 1\\);.*" "next to longjmp (1)"
 
+setup_kfail "gdb/9270" "x86_64-*-*"
 set msg "next over longjmp(1)"
 gdb_test_multiple "next" $msg {
     -re ".*patt1.*$gdb_prompt $" {
@@ -103,6 +104,7 @@ gdb_test "break $bp_miss_step_2" \
 
 gdb_test "next" "call_longjmp.*" "next over setjmp (2)"
 
+setup_kfail "gdb/9270" "x86_64-*-*"
 set msg "next over call_longjmp (2)"
 gdb_test_multiple "next" $msg {
     -re ".*patt2.*$gdb_prompt $" {
@@ -127,4 +129,5 @@ gdb_test "break $bp_start_test_3" \
     "breakpoint at pattern 3 start"
 gdb_test "continue" "patt3.*" "continue to breakpoint at pattern 3 start"
 
+setup_kfail "gdb/9270" "x86_64-*-*"
 gdb_test "next" "longjmp caught.*" "next over patt3"


             reply	other threads:[~2010-03-18 22:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18 22:16 Doug Evans [this message]
2010-03-18 22:33 ` Mark Kettenis
2010-03-18 23:42   ` Doug Evans
2010-03-18 23:41 ` Doug Evans
2010-03-19  0:58   ` Joseph S. Myers
2010-03-19  3:29     ` Doug Evans
2010-03-19  1:50   ` Tom Tromey
2010-03-19  2:19     ` Joseph S. Myers
2010-03-19  1:46 ` Daniel Jacobowitz

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=20100318221601.F233684413@ruffy.mtv.corp.google.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    /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