You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding an RPATH to an executable without an RPATH moves the elf note segment containing the GNU Build ID to the end of the file. This renders it impossible to extract the Build ID from a core dump as it is no longer loaded into process memory. This note segment corresponds to the section .note.gnu.build-id and is deliberately placed at the beginning of the elf file.
It is still contained in the binary and can be extracted with tools like readelf, but it will not be loaded into process memory and is therefore not part of a core dump.
I don't care about other elf notes, only this one.
Among other tools, gdb has debuginfod support and can download executables and debug symbols if the Build ID can be extracted from a core dump.
The text was updated successfully, but these errors were encountered:
Adding an RPATH to an executable without an RPATH moves the elf note segment containing the GNU Build ID to the end of the file. This renders it impossible to extract the Build ID from a core dump as it is no longer loaded into process memory. This note segment corresponds to the section .note.gnu.build-id and is deliberately placed at the beginning of the elf file.
It is still contained in the binary and can be extracted with tools like readelf, but it will not be loaded into process memory and is therefore not part of a core dump.
I don't care about other elf notes, only this one.
Among other tools, gdb has debuginfod support and can download executables and debug symbols if the Build ID can be extracted from a core dump.
The text was updated successfully, but these errors were encountered: