All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cody P Schafer <devel-lists@codyps.com>
To: crash-utility@redhat.com, kexec@lists.infradead.org
Subject: given a makedumpfile processed coredump, generate a symbolic backtrace containing the same info as a standard gdb backtrace
Date: Mon, 09 Sep 2013 16:06:39 -0700	[thread overview]
Message-ID: <522E547F.5030001@codyps.com> (raw)


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

                 reply	other threads:[~2013-09-09 23:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=522E547F.5030001@codyps.com \
    --to=devel-lists@codyps.com \
    --cc=crash-utility@redhat.com \
    --cc=kexec@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.