From: Michael Eager <eager@eagerm.com>
To: Paul Koning <Paul_Koning@Dell.com>
Cc: gdb@sourceware.org
Subject: Re: Backtrace from kernel to user space in coredump
Date: Mon, 14 Jun 2010 03:18:00 -0000 [thread overview]
Message-ID: <4C159F8E.40303@eagerm.com> (raw)
In-Reply-To: <D8CEBB6AE9D43848BD2220619A43F32665BBEE@M31.equallogic.com>
Paul Koning wrote:
> I've done just what you describe for MIPS, by adding a bunch of code to the
> prologue analyzers. The user space symbols are a bit of a hassle, not so
> much for the program itself (add-symbol-file is easy enough for that) but
> because of the shared libraries (if you have those -- in my case it was
> NetBSD so that did matter).
Is this in the gdb repo or elsewhere? I looked a the prologue
code for MIPS and it looks pretty vanilla.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next prev parent reply other threads:[~2010-06-14 3:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-12 13:06 Michael Eager
2010-06-12 15:19 ` Frédéric RISS
2010-06-12 16:16 ` Paul Koning
2010-06-14 3:18 ` Michael Eager [this message]
2010-06-14 7:23 ` Hui Zhu
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=4C159F8E.40303@eagerm.com \
--to=eager@eagerm.com \
--cc=Paul_Koning@Dell.com \
--cc=gdb@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox