From 9de00a4aa026297eae42bafd8ab413cfc1a53e3a Mon Sep 17 00:00:00 2001 From: Pedro Alves Date: Fri, 7 Nov 2014 15:20:47 +0000 Subject: [PATCH] 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 PR gdb/17511 * gdb.base/sigstep.exp (in_handler_map) : xfail i?86-*-linux*. --- gdb/testsuite/ChangeLog | 6 ++++++ gdb/testsuite/gdb.base/sigstep.exp | 1 + 2 files changed, 7 insertions(+) diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 7983271..6187c74 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,9 @@ +2014-11-07 Pedro Alves + + PR gdb/17511 + * gdb.base/sigstep.exp (in_handler_map) : xfail + i?86-*-linux*. + 2014-11-03 Siva Chandra Reddy PR c++/17494 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)" -- 2.7.4