diff options
| author | Pedro Alves <palves@redhat.com> | 2014-11-07 15:20:47 +0000 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2014-11-07 15:20:47 +0000 |
| commit | 9de00a4aa026297eae42bafd8ab413cfc1a53e3a (patch) | |
| tree | f3f64fd4f8b6d74661282bf348a2cca8f2bb1216 /ld | |
| parent | b7a084bebe979a4743540349025561ce82208843 (diff) | |
| download | gdb-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 'ld')
0 files changed, 0 insertions, 0 deletions