> I'll keep digging.
The problem is that KGDB isn't prepared to deal with the non-blocking serial
port reads that matt's commit introduced in 2013 (am I really the first one to
try this on bare metal since then?)
Where the read function `com_common_getc` used to block, it will now return -1,
w
> > There is no delay between ``kgdb waiting...'' and ``fatal breakpoint trap
> > in supervisor mode''.
>
> Looks like that behavior was introduced by the following commit
> to src/sys/arch/i386/i386/trap.c:
>
>
> revision 1.239
> date: 2008-05-30 13:38:21 +030
I am a bit fuzzy on the details, but definitely in 2010 on netbsd-5
remote kgdb on i386 worked. I am 95% sure it still worked on netbsd-6
in 2011/2012.
pgpyUX2NLYXRt.pgp
Description: PGP signature
Timo Buhrmester wrote:
> Using a GENERIC kernel with only the modifications required to enable KGDB
> (see bottom for config diff), I get the following behavior on the TARGET
> machine:
> | > boot netbsd -d
> | 15741968+590492+466076 [689568+730405]=0x1161fd4
> | kernel text is mapped with 4 larg
I'm failing to get KGDB on i386 working for kernel debugging over a serial
(nullmodem) link, as described in http://www.netbsd.org/docs/kernel/kgdb.html
The TARGET (to-be-debugged) system has two serial ports, com0 is the boot
console, com1 is what I set KGDB to operate on.
The REMOTE (debugger)
