From: Michael Snyder <msnyder@vmware.com>
To: Michael Snyder <msnyder@vmware.com>,
Eric Cooper <Eric.Cooper@citrix.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Reconstructing corrupt stacks/patching frame pointers
Date: Thu, 11 Dec 2008 18:05:00 -0000 [thread overview]
Message-ID: <4941555D.6020205@vmware.com> (raw)
In-Reply-To: <20081211023236.GA17606@caradoc.them.org>
Daniel Jacobowitz wrote:
> On Wed, Dec 10, 2008 at 03:16:32PM -0800, Michael Snyder wrote:
>> I presume this is a core dump from a Free BSD system.
>>
>> Unfortunately, for the most part, the folks here in the gdb
>> maintainer group don't play a very active role in maintaining
>> the bits for gdb on BSD. Somebody may correct me if I'm wrong...
>>
>> You may need to approach the Free BSD community for this.
>
> Well, Mark Kettenis does. But the problem is general to all core
> files; I've seen requests to change the $sp in Linux corefiles too.
It might be possible with a normal elf core file.
I know there is a mode that allows gdb to treat a
corefile as read-write. Lemme see... here it is:
"help set write".
Don't know whether it works for registers...
Don't know whether it works with fbsd kgdb...
next prev parent reply other threads:[~2008-12-11 18:05 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
2008-12-10 23:20 ` Michael Snyder
2008-12-11 2:33 ` Daniel Jacobowitz
2008-12-11 18:05 ` Michael Snyder [this message]
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=4941555D.6020205@vmware.com \
--to=msnyder@vmware.com \
--cc=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