The test is disabled. It fails because Valgrind is not stopping at the specified breakpoint.
Comment says
# test that gdbserver/gdb properly handle a PIC executable
# On linux, this implies a proper transfer of the auxv
# information via the gdbserver protocol packet qXfer:auxv:read:
# The content of the auxv data can be shown by gdb using
# gdb command 'info auxv'
So try info auxv.
Also try -d x4 (the code has dlog(4 for auxv).
Compilation is disabled
-fPIC with clang and FLAG_PIE with ld
What does PIE do? -pie is the option and it causes the exe to be loadable anywhere (rather than a fixed place like 0x200000)
(gdb) info auxv
No auxiliary vector found, or failed reading it.
I tried vgdb -d -d -d -d anmd no sign of qXfer:auxv:read:
The test is disabled. It fails because Valgrind is not stopping at the specified breakpoint.
Comment says
So try info auxv.
Also try -d x4 (the code has dlog(4 for auxv).
Compilation is disabled -fPIC with clang and FLAG_PIE with ld
What does PIE do? -pie is the option and it causes the exe to be loadable anywhere (rather than a fixed place like 0x200000)
(gdb) info auxv No auxiliary vector found, or failed reading it.
I tried vgdb -d -d -d -d anmd no sign of qXfer:auxv:read: