New comment by oreo639 on void-packages repository

https://github.com/void-linux/void-packages/issues/49207#issuecomment-1987116052

Comment:
> is the intended behavior?

I can't speak for what the other Void maintainers intend, but afaict it is working as it is written. In this case, you can use substitute-path to fix the locations for the includes.
For source files you can can download the un-patched sources from https://sources.voidlinux.org (this won't include patches and compile-time generated files though, so be aware of that. For example, the header in this instance is a compile-time generated file.)
Ofc you can also use `disas` in gdb to see the assembly. 

Arch Linux, for example, uses debugedit to generate a list of source files referenced in the debug symbols to add them to the dbg packages: https://gitlab.archlinux.org/pacman/pacman/-/blob/master/scripts/libmakepkg/tidy/strip.sh.in#L38-53