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 <[EMAIL PROTECTED]> > To: Dag-Erling Smorgrav <[EMAIL PROTECTED]> > Cc: Yonny Cardenas B. <[EMAIL PROTECTED]>, [EMAIL PROTECTED], > [EMAIL PROTECTED] > Subject: Re: Kernel programming > > Thus spake Dag-Erling Smorgrav ([EMAIL PROTECTED]): > > > > 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 [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
