26 июн. 2009 г. · The core file/deployed executable is completely devoid of any sort of symbols. When I load it up in gdb and do a bt, the best I get is this:

15 окт. 2021 г. · You can give GDB a binary with debug symbols instead of the binary which actually produced the core. The best practice is to always build with debug symbols.

29 янв. 2017 г. · I got this weird crash and I have no idea how to debug the core dump since the call stack is missing symbols info for some reason, except for the last function.

11 февр. 2011 г. · To compile your process with the debugging information (symbols and dwarfs for lines, types, ...), you need to add -g in your compiler flags.

15 июн. 2020 г. · The core dump comes from another system that is experiencing some issues. I have copied the core over to my dev system to examine it. I go into ...

4 авг. 2014 г. · Use gdb and the binary without debug symbols to look at the core: $ gdb -q ./crash core warning: ~/.gdbinit.local: No such file or directory ...

28 янв. 2012 г. · I have a core dump of an executable that was NOT built with debug symbols. Can I recover argv contents to see what the command line was? If I ...

1 июл. 2023 г. · I have a core dump file that needs to be debugged. But the only file that I have for crashed program is a debug symbols file.

4 нояб. 2022 г. · If I don't pass the non-stripped file as argument, the function names are not displayed. Yes: strip removes the symbols and debug info.

1 дек. 2010 г. · You don't need debug symbols for libc to get the stack trace. You wouldn't get file and line numbers without debug symbols, but you should get ...