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*.
This commit is contained in:
parent
b7a084bebe
commit
9de00a4aa0
@ -1,3 +1,9 @@
|
||||
2014-11-07 Pedro Alves <palves@redhat.com>
|
||||
|
||||
PR gdb/17511
|
||||
* gdb.base/sigstep.exp (in_handler_map) <si+advance>: xfail
|
||||
i?86-*-linux*.
|
||||
|
||||
2014-11-03 Siva Chandra Reddy <sivachandra@google.com>
|
||||
|
||||
PR c++/17494
|
||||
|
@ -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)"
|
||||
|
Loading…
x
Reference in New Issue
Block a user