async-crashdump-debugging-initiative icon indicating copy to clipboard operation
async-crashdump-debugging-initiative copied to clipboard

Published 20 hours ago • verified publisher icon rust-lang

Document build-id handling

Open frehberg opened this issue 2 years ago • 0 comments

If anybody wants to analyze a crash-dump (core) file, the specific debug symbols of the binary in question are required.

Each ELF binary being built contains a build-id (kind of fingerprint of the binary). This build-id can be read from crash-dump file and can be used to search for the corresponding ELF binaries (exec and libs) in archive.

This way, the gdb tool can be invoked with matching debug symbols.

The concept of "build-id" should be documented in this book, otherwise people might wonder why having issues with stacktraces.

Please feel free to copy from my blog post explaining handling of build-ids

https://frehberg.com/2019/05/rust-handling-executables-and-their-debug-symbols/

frehberg avatar Feb 10 '22 09:02 frehberg