forked from Imagelibrary/binutils-gdb
d51a931152
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
b5e7cd5cd3 ("[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>
63 lines
2.0 KiB
Plaintext
63 lines
2.0 KiB
Plaintext
# Copyright 2022-2024 Free Software Foundation, Inc.
|
|
|
|
# This program is free software; you can redistribute it and/or modify
|
|
# it under the terms of the GNU General Public License as published by
|
|
# the Free Software Foundation; either version 3 of the License, or
|
|
# (at your option) any later version.
|
|
#
|
|
# This program is distributed in the hope that it will be useful,
|
|
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
# GNU General Public License for more details.
|
|
#
|
|
# You should have received a copy of the GNU General Public License
|
|
# along with this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
# Test "until LINE", started in the "main()" frame, where the until
|
|
# command runs into a longjmp that lands in a frame that is inner than
|
|
# main. GDB internally intercepts the longjmp, sets a breakpoint at
|
|
# the jump destination, and once there, decides whether to stop or
|
|
# ignore the breakpoint hit depending on whether the initiating frame
|
|
# is present on the frame chain. GDB used to have a bug where it
|
|
# recorded the frame of the caller of main instead of the frame of
|
|
# main as the initiating frame, and then later on when deciding
|
|
# whether the longjmp landed somewhere inner than main, since
|
|
# unwinding normally stops at main, GDB would fail to find the
|
|
# initiating frame.
|
|
|
|
standard_testfile
|
|
|
|
if {[prepare_for_testing "failed to prepare" ${testfile} ${srcfile}]} {
|
|
return
|
|
}
|
|
|
|
if {![runto_main]} {
|
|
return
|
|
}
|
|
|
|
set have_longjmp_probe [have_longjmp_probe]
|
|
|
|
delete_breakpoints
|
|
|
|
set until_to_line [gdb_get_line_number "until to here"]
|
|
|
|
set re_cannot_insert_bp \
|
|
[multi_line \
|
|
"Warning:" \
|
|
"Cannot insert breakpoint $::decimal\\." \
|
|
"Cannot access memory at address $::hex"]
|
|
|
|
set test "until \$line, in main"
|
|
gdb_test_multiple "until $until_to_line" $test {
|
|
-re -wrap "\r\n$re_cannot_insert_bp\r\n.*" {
|
|
if { $have_longjmp_probe } {
|
|
fail $gdb_test_name
|
|
} else {
|
|
kfail gdb/26967 $gdb_test_name
|
|
}
|
|
}
|
|
-re -wrap " until to here .*" {
|
|
pass $gdb_test_name
|
|
}
|
|
}
|