Table of Contents
Recommended
Over the past few weeks, some of our users have informed us that they have encountered a basic debug file without GDB.
I want to return to access to the saved images by simply dumping the kernel of a program that has no debug symbols (I feel the need to do this in C). When I open the program, and thus the kernel dump in GDB, I get a stack trace with the function names. For example:
(gdb) bt# 0 0x08048443 on layer 3 ()# 1 0x08048489 in layer2 ()# 2 0x080484c9 in layer1 ()# 3 0x0804854e when it comes to main ()
The names of all functions are stored in the exe in the .strtab section. How can I build a stack for tracing with different images? It is not possible to run GDB in batch mode. And just “copy this, you see that parts of gdb were used” is also a bad idea, because the code is not written independently of each other.
To ask my question in more detail, where can I find use in a kernel dump, where can I start reading the stack details? Is there some kind of library to access this information? Any framework I can use? Or maybe better, some documentation on how this information is structured in an abdominal dump?
(I’ve already seen the question “How can I generate a stack trace from an actual file givein memory in No Celsius, calling an external tool, for example, mainly because of gdb “, but since there is no correct answer, I thought, I’ll ask again)
30.1k
