Neeraj kushwaha wrote:
Hi All,
This is what I'm trying to do, I have a pretty extensive module for linux which does oops and panic once in a while.
After the panic, I would like to find out from the coredump where the panic happened and why it happened.
This would require examining the stack trace for the task that caused the dump and also the local variables on the function stack. I can get the stack trace using "trace" which is great
but is there any way to get into the stack look at the local variables for each of the functions on the stack, like gdb?
Can anyone rescue me on this issue or give some idea how to go about it to implement it.
The short answer is no, but you can use "bt -f" to dump
the stack contents of each frame, and figure out where
your local variables lie from a disassembly of the
function.
Dave
Thanks & Regards
Neeraj
--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/crash-utility
