Re: [patch 8/8] x86/vdso: Implement __vdso_futex_robust_try_unlock()

[Sebastian Andrzej Siewior]

On 2026-03-19 08:41:47 [+0100], Thomas Weißschuh wrote:
> > vdso2c picks them up correctly too.
> 
> What also works is to have GDB look up the debug symbols through their
> debug ids. At this point the load address of the vDSO is already known.
> 
> $ make vdso_install INSTALL_MOD_PATH=$SOME_DIRECTORY
> $ gdb -ex "set debug-file-directory $SOME_DIRECTORY/lib/modules/$(uname -r)/vdso" $BINARY
> 
> Depending on the distribution the vDSO from the kernel package might already
> be set up to be found automatically.
> 
> Maybe we could add a helper to scripts/gdb/ which uses $(vdso-install-y)
> to either populate a debug-file-directory automatically or hook into the GDB
> lookup process to avoid these manual steps.

Is this a complete vdso.so as mapped in process or just the debug
symbols or both?
Looking at my Debian thingy this seems to be there as of
	https://packages.debian.org/sid/amd64/linux-image-6.19.8+deb14-amd64-dbg/filelist

| /usr/lib/debug/lib/modules/6.19.8+deb14-amd64/vdso/vdso32.so
| /usr/lib/debug/lib/modules/6.19.8+deb14-amd64/vdso/vdso64.so
| /usr/lib/debug/lib/modules/6.19.8+deb14-amd64/vdso/vdsox32.so
| /usr/lib/debug/lib/modules/6.19.8+deb14-amd64/vmlinux

or do we talk about other things? Usually there is -dbgsym with the
stripped out debug symbols under /usr/lib/debug/.build-id/ but the
kernel seems different.

> Thomas

Sebastian