From owner-freebsd-hackers  Fri Nov 14 09:59:50 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id JAA18468
          for hackers-outgoing; Fri, 14 Nov 1997 09:59:50 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from trojanhorse.ml.org (mdean.vip.best.com [206.86.94.101])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA18448
          for <hackers@freebsd.org>; Fri, 14 Nov 1997 09:59:42 -0800 (PST)
          (envelope-from jamil@trojanhorse.ml.org)
Received: from localhost (jamil@localhost)
	by trojanhorse.ml.org (8.8.8/8.8.5) with SMTP id JAA00861
	for <hackers@freebsd.org>; Fri, 14 Nov 1997 09:59:24 -0800 (PST)
Date: Fri, 14 Nov 1997 09:59:24 -0800 (PST)
From: "Jamil J. Weatherbee" <jamil@trojanhorse.ml.org>
To: hackers@freebsd.org
Subject: Kernel Debugging
Message-ID: <Pine.BSF.3.96.971114095609.855A-100000@trojanhorse.ml.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



I am trying to track down a driver bug, however I've figured out that
using DDB I can get the funtion name and code offset on a panic. But how
do I figure out what C line that is in the source?

I know how to do this with a  user process running gdb, but I am a little
confused here as to how you get debugging info into the kernel binary?