aboutsummaryrefslogtreecommitdiff
path: root/gdbsupport/gdb_obstack.h
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2024-03-20 19:23:48 +0100
committerTom de Vries <tdevries@suse.de>2024-03-20 19:23:48 +0100
commitd51a931152993fb095fd52083f2ba17d19e32ffd (patch)
treeca78455e9c20d5a8fe38258a6b81d6da74e5959c /gdbsupport/gdb_obstack.h
parentd391f3721e20d160909a3afae7fee647ea5575a2 (diff)
downloadbinutils-d51a931152993fb095fd52083f2ba17d19e32ffd.zip
binutils-d51a931152993fb095fd52083f2ba17d19e32ffd.tar.gz
binutils-d51a931152993fb095fd52083f2ba17d19e32ffd.tar.bz2
[gdb/testsuite] Add PR gdb/26967 KFAIL in two more test-cases
On aarch64-linux (debian 12), when running test-case gdb.base/longjmp-until-in-main.exp, I run into: ... (gdb) until 33^M warning: Breakpoint address adjusted from 0x70f727c678928489 to 0xfff727c678928489.^M Warning:^M Cannot insert breakpoint 0.^M Cannot access memory at address 0xfff727c678928489^M ^M 0x0000fffff7e3a580 in siglongjmp () from /lib/aarch64-linux-gnu/libc.so.6^M (gdb) FAIL: gdb.base/longjmp-until-in-main.exp: until $line, in main ... This is PR gdb/26967: no longjmp probe is available: ... (gdb) info probes stap libc ^longjmp$^M No probes matched.^M ... and glibc applies pointer mangling which makes it fairly difficult for gdb to get the longjmp target. There's a KFAIL for this in test-case gdb.base/longjmp.exp, added in commit b5e7cd5cd3d ("[gdb/testsuite] Add KFAILs in gdb.base/longjmp.exp"). Factor out new proc have_longjmp_probe, and use it to add similar KFAIL in this and one more test-case. Tested on aarch64-linux. Approved-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'gdbsupport/gdb_obstack.h')
0 files changed, 0 insertions, 0 deletions