Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: [obv] testsuite: disp-step-syscall.exp: Setup KFAIL for PR server/13796
Date: Sat, 03 Mar 2012 07:01:00 -0000	[thread overview]
Message-ID: <20120303070105.GA13581@host2.jankratochvil.net> (raw)

Hi,

[patch] Fix disp-step-syscall.exp on some i386 targets
http://sourceware.org/ml/gdb-patches/2012-02/msg00635.html

just fixed a testcase which revealed existing IMO gdbserver Bug, therefore
just KFAILed it.

stepi
Program terminated with signal SIGILL, Illegal instruction.
The program no longer exists.
(gdb) PASS: gdb.base/disp-step-syscall.exp: vfork: single step over vfork
Child terminated with signal = 0x4 (SIGILL)
GDBserver exiting
print /x $pc
No registers.
(gdb) FAIL: gdb.base/disp-step-syscall.exp: vfork: get hexadecimal valueof "$pc" (timeout)

->
http://sourceware.org/bugzilla/show_bug.cgi?id=13796


Regards,
Jan


http://sourceware.org/ml/gdb-cvs/2012-03/msg00073.html

--- src/gdb/testsuite/ChangeLog	2012/03/02 20:36:39	1.3115
+++ src/gdb/testsuite/ChangeLog	2012/03/03 06:58:16	1.3116
@@ -1,3 +1,8 @@
+2012-03-03  Jan Kratochvil  <jan.kratochvil@redhat.com>
+
+	Setup KFAIL for PR server/13796.
+	* gdb.base/disp-step-syscall.exp (single step over vfork): Setup KFAIL.
+
 2012-03-02  Joel Brobecker  <brobecker@adacore.com>
 
 	* gdb.ada/operator_bp: New testcase.
--- src/gdb/testsuite/gdb.base/disp-step-syscall.exp	2012/02/29 14:59:41	1.6
+++ src/gdb/testsuite/gdb.base/disp-step-syscall.exp	2012/03/03 06:58:16	1.7
@@ -118,7 +118,20 @@
     gdb_test_no_output "set displaced-stepping on"
 
     # Check the address of next instruction of syscall.
-    gdb_test "stepi" ".*" "single step over $syscall"
+    if {$syscall == "vfork" && [is_remote target]} {
+	setup_kfail server/13796 "*-*-*"
+    }
+    set test "single step over $syscall"
+    gdb_test_multiple "stepi" $test {
+	-re "Program terminated with signal SIGILL,.*\r\n$gdb_prompt $" {
+	    fail $test
+	    return
+	}
+	-re "\r\n$gdb_prompt $" {
+	    pass $test
+	}
+    }
+
     set syscall_insn_next_addr_found [get_hexadecimal_valueof "\$pc" "0"]
 
     set test "single step over $syscall final pc"


             reply	other threads:[~2012-03-03  7:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03  7:01 Jan Kratochvil [this message]
2012-03-03 14:30 ` Yao Qi
2012-03-03 14:34   ` Jan Kratochvil
2012-03-03 15:17 ` Pedro Alves

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=20120303070105.GA13581@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.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