aboutsummaryrefslogtreecommitdiff
path: root/gdb/python/python-config.py
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2024-03-28 08:26:31 +0100
committerTom de Vries <tdevries@suse.de>2024-03-28 08:26:31 +0100
commit4ef6173d2dfeafd33deedf7ce0d384cfbcf1170d (patch)
treee33cc911b9a57544a58eadeee18452fbbc1d061f /gdb/python/python-config.py
parenta26b7d06eb20bf8c83c9204a398c3444b5c28ddb (diff)
downloadbinutils-4ef6173d2dfeafd33deedf7ce0d384cfbcf1170d.zip
binutils-4ef6173d2dfeafd33deedf7ce0d384cfbcf1170d.tar.gz
binutils-4ef6173d2dfeafd33deedf7ce0d384cfbcf1170d.tar.bz2
[gdb/testsuite] Fix gdb.base/ending-run.exp on manjaro linux
On aarch64-linux, using the manjaro linux distro, I run into: ... (gdb) next^M 32 }^M (gdb) next^M 0x0000fffff7d67b80 in ?? () from /usr/lib/libc.so.6^M (gdb) FAIL: gdb.base/ending-run.exp: step out of main ... What happens here is described in detail in this clause: ... -re "0x.*\\?\\? \\(\\) from /lib/powerpc.*$gdb_prompt $" { # This case occurs on Powerpc when gdb steps out of main and the # needed debug info files are not loaded on the system, preventing # GDB to determine which function it reached (__libc_start_call_main). # Ideally, the target system would have the necessary debugging # information, but in its absence, GDB's behavior is as expected. ... } ... but the clause only matches for powerpc. Fix this by: - making the regexp generic enough to also match /usr/lib/libc.so.6, and - updating the comment to not mention powerpc. Tested on aarch64-linux. PR testsuite/31450 Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31450
Diffstat (limited to 'gdb/python/python-config.py')
0 files changed, 0 insertions, 0 deletions