From: "Eric Cooper" <Eric.Cooper@citrix.com>
To: <gdb@sourceware.org>
Subject: Reconstructing corrupt stacks/patching frame pointers
Date: Tue, 09 Dec 2008 23:28:00 -0000 [thread overview]
Message-ID: <2108A3A691C70B41B22A8C5ED3725423024DA3FA@sjcpexch02.citrite.net> (raw)
In-Reply-To: <2108A3A691C70B41B22A8C5ED3725423024DA3F9@sjcpexch02.citrite.net>
Hello,
I have a kernel core dump with a corrupt stack and I can identify the stack location that is corrupted and what it should be and I want to write the correct frame pointer to the stack so that bt and frame x work. I have tried that using the "set" command and it says:
kvm_write not implemented for dead kernels.
I see this code is in kvm-fbsd.c (I am using BSD) and I have hacked around a little bit to allow the write but ultimately it fails on writes to /dev/kmem. Is there a reasonable way to do what I want to achieve?
Thanks in advance,
Eric
next parent reply other threads:[~2008-12-09 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2108A3A691C70B41B22A8C5ED3725423024DA3F9@sjcpexch02.citrite.net>
2008-12-09 23:28 ` Eric Cooper [this message]
2008-12-10 23:20 ` Michael Snyder
2008-12-11 2:33 ` Daniel Jacobowitz
2008-12-11 18:05 ` Michael Snyder
2008-12-11 18:19 ` Daniel Jacobowitz
2008-12-12 0:17 ` Michael Snyder
2008-12-12 1:04 ` Daniel Jacobowitz
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=2108A3A691C70B41B22A8C5ED3725423024DA3FA@sjcpexch02.citrite.net \
--to=eric.cooper@citrix.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