Date: Wed, 24 Jan 2001 13:03:08 -0500 (EST) From: AARON J MARKS <ajmarks@dsl.cis.upenn.edu> To: ycardena@yahoo.com Cc: hackers@freebsd.org, Ronald Minnich <rminnich@lanl.gov> Subject: Re: Kernel programming (fwd) Message-ID: <Pine.SOL.4.21.0101241258530.5276-100000@codex.cis.upenn.edu> In-Reply-To: <Pine.LNX.4.30.0101230809520.17177-100000@mini.acl.lanl.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
Have you tried remote gdb kernel debugging yet? It's documented in the handbook also. I found it to be very easy to do and *much* better than debugging on the same machine. All you need is a serial cable and a spare FreeBSD machine. I used it to debug a module, but it would work just as well on the kernel itself. -A. On Tue, 23 Jan 2001, Ronald G Minnich wrote: > ---------- Forwarded message ---------- > Date: Tue, 23 Jan 2001 12:20:56 +0100 > From: Alexander Langer <alex@FreeBSD.ORG> > To: Dag-Erling Smorgrav <des@ofug.org> > Cc: Yonny Cardenas B. <ycardena@yahoo.com>, questions@FreeBSD.ORG, > hackers@FreeBSD.ORG > Subject: Re: Kernel programming > > Thus spake Dag-Erling Smorgrav (des@ofug.org): > > > > There recently (last week or something) was a thread here or on > > > another mailinglist on how to debug kernel moduls, which is a little > > > bit tricky. > > It's also documented in the handbook. > > Well, actually debugging modules is a little bit more tricky than > debugging kernels with statically linked drivers. > > This is what I meant. > > Alex > -- > cat: /home/alex/.sig: No such file or directory > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SOL.4.21.0101241258530.5276-100000>