From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11855 invoked by alias); 10 Dec 2008 23:20:48 -0000 Received: (qmail 11845 invoked by uid 22791); 10 Dec 2008 23:20:47 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.115.85.69) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 10 Dec 2008 23:20:12 +0000 Received: from mailhost5.vmware.com (mailhost5.vmware.com [10.16.68.131]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id AA5E313038; Wed, 10 Dec 2008 15:20:10 -0800 (PST) Received: from [10.20.92.151] (promb-2s-dhcp151.eng.vmware.com [10.20.92.151]) by mailhost5.vmware.com (Postfix) with ESMTP id 9F5ACDC0B5; Wed, 10 Dec 2008 15:20:10 -0800 (PST) Message-ID: <49404DD0.60602@vmware.com> Date: Wed, 10 Dec 2008 23:20:00 -0000 From: Michael Snyder User-Agent: Thunderbird 1.5.0.12 (X11/20080411) MIME-Version: 1.0 To: Eric Cooper CC: "gdb@sourceware.org" Subject: Re: Reconstructing corrupt stacks/patching frame pointers References: <2108A3A691C70B41B22A8C5ED3725423024DA3F9@sjcpexch02.citrite.net> <2108A3A691C70B41B22A8C5ED3725423024DA3FA@sjcpexch02.citrite.net> In-Reply-To: <2108A3A691C70B41B22A8C5ED3725423024DA3FA@sjcpexch02.citrite.net> Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-12/txt/msg00034.txt.bz2 Eric Cooper wrote: > 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? 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.