[Bug testsuite/33541] New: [gdb/testsuite] Introduce require have_prelink_support
vries at gcc dot gnu.org
sourceware-bugzilla@sourceware.org
Tue Oct 14 09:00:54 GMT 2025
https://sourceware.org/bugzilla/show_bug.cgi?id=33541
Bug ID: 33541
Summary: [gdb/testsuite] Introduce require have_prelink_support
Product: gdb
Version: unknown
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
I build gdb on ubuntu 24.04.3, and ran the testsuite.
I ran into a few failures, all prelink-related AFAICT:
...
$ ./sum.sh
1 gdb.base/attach-pie-misread.exp:
159 gdb.base/break-interp.exp:
1 gdb.base/prelink.exp:
...
The first in more detail:
...
Command is exec /usr/sbin/prelink -qNR --no-exec-shield
--dynamic-linker=/home/vries/gdb/build/gdb/testsuite/outputs/gdb.base/attach-pie-misread/attach-pie-misread.d/ld-linux-x86-64.so.2
--ld-library-path=/home/vries/gdb/build/gdb/testsuite/outputs/gdb.base/attach-pie-misread/attach-pie-misread.d
/home/vries/gdb/build/gdb/testsuite/outputs/gdb.base/attach-pie-misread/attach-pie-misread
/home/vries/gdb/build/gdb/testsuite/outputs/gdb.base/attach-pie-misread/attach-pie-misread.d/libc.so.6
/home/vries/gdb/build/gdb/testsuite/outputs/gdb.base/attach-pie-misread/attach-pie-misread.d/ld-linux-x86-64.so.2
result is 1
output is prelink:
/home/vries/gdb/build/gdb/testsuite/outputs/gdb.base/attach-pie-misread/attach-pie-misread:
Could not parse ` linux-vdso.so.1 (0x00007e913ae7f000)'
FAIL: gdb.base/attach-pie-misread.exp: prelink ld-linux-x86-64.so.2
...
I went to read a bit about prelink, and found out that after installing
prelink, there's some setup to do, like setting PRELINKING=yes in
/etc/default/prelink.
I have not done such a setup, so perhaps these tests fail because of an
incomplete setup.
If so, there should be some have_prelink_support proc (to be used with require
in those test-cases), that does something more than just make sure that the
prelink binary is present.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Gdb-prs
mailing list