To: "tech-kern@NetBSD.ORG" <tech-kern@NetBSD.ORG>
Subject: Re: Debugging tools...

Frank van der Linden <frank@wins.uva.nl> wrote:
> 
...
> I'm not exactly sure what you are trying to debug, but there is also
> kgdb via a serial line. Compile a kernel with
> 
> makeoptions     DEBUG="-g"
...
> on the other machine, given that the nulmodem cable is plugged in to
> the 3rd serial port there:
> 
> 	% cd <your_compile_dir>
> 	% gdb
> 	(gdb) set remotebaud 38400
> 	(gdb) set remotebreak
> 	(gdb) target remote /dev/tty02
> 
> Once the connection has been established, you can use gdb as you would
> normally.
> 
> - Frank

Nice, but I think from mails in the past there is also a way to do similar
things with one computer. Not as comfortable as whith gbd, but posible.

I want to debug the SCSI scanner driver, which hangs the system in the
boot sequenze, if the scanner is switched on.

Because the Scanner hangs the Windows-Software also, if it is
connected thrue an Adapdec Controller, as long I dosen't start an
other Collel-SCSI-Utility befor, I asume something go wrong at the
initialisation of the scanner.

In addition I like to hear opinions on the following questions:

1. Should I use a separate disk to debug that, or can I work with my
working disk, whithout to much risk of loosing all data (I will make a
backup of it anyway)?

2. If you find it to dangerous to use the working disk for that, should
I disconnect them when using a FD to boot from?

3. How I have to configure the kernel for debuging a driver whitout a
second computer?

-- Bernd