Hi Keith and the rest of the gang,
I would like to know some rather basic questions answered. I could not make
out much from the available documnetations.
The following are my questions:
1) How is debugging done in a multi-processor environment ?
2) Does kdb/kdgb support debugging in a SMP environment ?
3) Could anyone let me know the limitations kdb/kgdb has in an SMP environment?
4) Can non-maskable interrupts be sent across processors while debugging?
anyone has anyidea of Dprobes limitations and strenghts in the same context,
please throw light on the same.
Thank you all in advance.
From: Keith Owens [mailto:kaos@xxxxxxx]
Sent: Thu 14-Nov-02 6:19 AM
Subject: Re: kdb from COM1: doesn't work with ctrl-A
On Wed, 13 Nov 2002 15:23:23 -0800,
"Chess ForFun" <chessforfun@xxxxxxxxxxx> wrote:
Please do not use HTML on this list, plain text is much better.
>I have installed latest kdb patches for 2.4.19 kernel and kdb seems to
>be working fine on both machines. But when I try to debug from a serial
>console, I can't get into the debugger. I tried hitting CTRL-A, send a
>break key using kermit and minicom, nothing seems to work.
>COM1 port of debug machine is connected to another linux machine's
>COM1 port. If I do "ls > /dev/ttyS0" then output comes there. I can
>also get lilo output on serial console. This confirms that serial
>console is working fine.
>Does this combination work for anyone?
You have to have a user space program reading from the serial port.
Otherwise the linux serial code does not look at any characters coming
down the line, this is a restriction of the linux serial layer. My
co:2345:respawn:/sbin/agetty -L ttyS0 38400 vt100