aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.base/sigstep.exp
diff options
context:
space:
mode:
authorPedro Alves <palves@redhat.com>2014-11-07 15:20:47 +0000
committerPedro Alves <palves@redhat.com>2014-11-07 15:20:47 +0000
commit9de00a4aa026297eae42bafd8ab413cfc1a53e3a (patch)
treef3f64fd4f8b6d74661282bf348a2cca8f2bb1216 /gdb/testsuite/gdb.base/sigstep.exp
parentb7a084bebe979a4743540349025561ce82208843 (diff)
downloadgdb-9de00a4aa026297eae42bafd8ab413cfc1a53e3a.zip
gdb-9de00a4aa026297eae42bafd8ab413cfc1a53e3a.tar.gz
gdb-9de00a4aa026297eae42bafd8ab413cfc1a53e3a.tar.bz2
gdb.base/sigstep.exp: xfail gdb/17511 on i?86 Linux
Running gdb.base/sigstep.exp with --target=i686-pc-linux-gnu on a 64-bit kernel naturally trips on PR gdb/17511 as well, given this is a kernel bug. I haven't really tested a real 32-bit kernel/machine, but given the code in question in the kernel is shared between 32-bit and 64-bit, I'm quite sure the bug triggers in those cases as well. So, simply xfail i?86-*-linux* too. gdb/testsuite/ 2014-11-07 Pedro Alves <palves@redhat.com> PR gdb/17511 * gdb.base/sigstep.exp (in_handler_map) <si+advance>: xfail i?86-*-linux*.
Diffstat (limited to 'gdb/testsuite/gdb.base/sigstep.exp')
-rw-r--r--gdb/testsuite/gdb.base/sigstep.exp1
1 files changed, 1 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.base/sigstep.exp b/gdb/testsuite/gdb.base/sigstep.exp
index c4580a7..4fea6be 100644
--- a/gdb/testsuite/gdb.base/sigstep.exp
+++ b/gdb/testsuite/gdb.base/sigstep.exp
@@ -155,6 +155,7 @@ set in_handler_map {
# subsequent PTRACE_CONTINUEs trapping after each
# insn.
if {$enter_cmd != "continue"} {
+ setup_xfail "i?86-*-linux*" gdb/17511
setup_xfail "x86_64-*-linux*" gdb/17511
}
fail "$test (spurious SIGTRAP)"