From owner-freebsd-hackers  Thu Mar 29  8:40:50 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id 9B37337B71B
	for <hackers@freebsd.org>; Thu, 29 Mar 2001 08:40:45 -0800 (PST)
	(envelope-from jdp@wall.polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.11.1/8.11.1) with ESMTP id f2TGeMV16580;
	Thu, 29 Mar 2001 08:40:22 -0800 (PST)
	(envelope-from jdp@wall.polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.11.3/8.11.0) id f2TGeB409150;
	Thu, 29 Mar 2001 08:40:11 -0800 (PST)
	(envelope-from jdp)
Date: Thu, 29 Mar 2001 08:40:11 -0800 (PST)
Message-Id: <200103291640.f2TGeB409150@vashon.polstra.com>
To: hackers@freebsd.org
From: John Polstra <jdp@polstra.com>
Reply-To: hackers@freebsd.org
Cc: bright@wintelcom.net
Subject: Re: ddb -> gdb help?
In-Reply-To: <20010328191653.B9431@fw.wintelcom.net>
References: <20010328191653.B9431@fw.wintelcom.net>
Organization: Polstra & Co., Seattle, WA
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In article <20010328191653.B9431@fw.wintelcom.net>,
Alfred Perlstein  <bright@wintelcom.net> wrote:
> I can't seem to get a crashdump, is there a way to take a 
> ddb crash address:  "Stopped at lf_setlock+0x52"
> and boot later and see what line of code that's on?

Assuming you have a corresponding kernel with debugging symbols, you
can do "gdb -k kernel.debug" and use the "info line" command to get
that information.

John

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message