Re: [Crash-utility] given a makedumpfile processed coredump, generate a symbolic backtrace containing the same info as a standard gdb backtrace

Crash's bt command doesn't provide function arguments/types as part of the backtrace (use bt not gdb's bt). There's an extension module here that may provide what you want: http://people.redhat.com/anderson/extensions.html#FP There a lot of history on the mailing list about wanting to use gdb's bt command if you want to have a read of it. -----Original Message----- From: crash-utility-bounces(a)redhat.com [mailto:crash-utility-bounces@redhat.com] On Behalf Of Cody P Schafer Sent: Tuesday, September 10, 2013 9:07 AM To: crash-utility(a)redhat.com; kexec(a)lists.infradead.org Subject: [Crash-utility] given a makedumpfile processed coredump, generate a symbolic backtrace containing the same info as a standard gdb backtrace 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. -- Crash-utility mailing list Crash-utility(a)redhat.com https://www.redhat.com/mailman/listinfo/crash-utility