Any idea how this is supposed to work...

I've set the TARGET machine up.. got the console working off boot on 
com0, and the kernel is compiled wth KGDB installed. When the TARGET 
machine boots with "boot -d".. it doesn't stop waiting for the REMOTE 
machine... and boots up regardless.

The com0 line in dmesg doesn't mention kgdb, but mentions console.

starting gdb on the REMOTE machine and trying to connect to the TARGET 
machine in attempt to "spike" it doesn't do anything.

Thanks in advance,
Phil.

In article <20050927145454.E7B9D236E8@thoreau.thistledown.com.au>, 
simonb@wasabisystems.com says...
> Phil Quinton wrote:
> 
> >  I have two machines, a REMOTE and TARGET machine. I want to run a 
> > serial console on the TARGET machine, so I can connect to it from say... 
> > minicom on the REMOTE machine.
> > 
> >  I also want to run kgdb, so I can kernel debug the TARGET machine from 
> > the REMOTE machine over the same serial port.
> > 
> >  Is this possible,
> 
> Allen Briggs added a "kgdb" command to ddb a couple of years back.
> Here's part of the commit message:
> 
>   Add a rudimentary 'trap to kgdb' command if KGDB is defined.  This allows
>   systems with only one serial port for console, etc., to have at least some
>   basic access to remote-kgdb-over-serial, even if it is a bit awkward.
> 
> I haven't used this myself, but it should be possbile...
> 
> Simon.
> --
> Simon Burge                            <simonb@wasabisystems.com>
> NetBSD Support and Service:         http://www.wasabisystems.com/
> 
>