public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
* given a makedumpfile processed coredump, generate a symbolic backtrace containing the same info as a standard gdb backtrace
@ 2013-09-09 23:06 Cody P Schafer
  0 siblings, 0 replies; only message in thread
From: Cody P Schafer @ 2013-09-09 23:06 UTC (permalink / raw)
  To: crash-utility, kexec


Hi all,

I've got a coredump file processed by makedumpfile (non-elf) and am 
trying to get a backtrace with all the line numbers, argument values, 
and argument types like a normal gdb backtrace with debug info (yes, I 
have a vmlinux built with debuginfo).

gdb refuses to load the core dump (no big supprise there). crash loads 
it but it's builtin backtrace doesn't appear to use debug info, and as a 
result doesn't give me arguments + types. Doing "gdb bt" complains about 
not having a stack.

Any advise? I see a few paths forward:

  - somehow get crash's gdb to understand where the stack is
  - hack gdb to load the non-elf coredump
  - modify makedumpfile to allow it to convert the non-elf coredump back 
to elf.

Thanks.

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2013-09-09 23:07 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-09-09 23:06 given a makedumpfile processed coredump, generate a symbolic backtrace containing the same info as a standard gdb backtrace Cody P Schafer

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox