Re: Kernel Debugging

From: George Anzinger (
Date: Fri Apr 28 2000 - 04:29:14 EST

I assume that the connection to the SysRq key was done because the ^C
did not work. Right? Sure would like to get ^C to work. Any hints?

For those who don't know:
A ^C from gdb is supposed to cause the target machine to break. This is
done by accepting interrupts from the serial card and looking for ^C in
the data stream.


Douglas Kilpatrick wrote:
> On Thu, 27 Apr 2000, Mani Manoharan Balaraman wrote:
> > The url is
> Ok. That's the remote debugging kernel patch...
> The patch available for 2.2 is (IMHO) broken. I have given them a revised
> patch, but no one has posted it to the web page.
> I have attached my revised patch to this message. Basically I fixed their
> problems with arg parce-ing, added a SysRq key to attach to the remote
> side, and integrated some changes Tigran (I believe) added to previous
> remote kernel debugging patches that somehow did not make the SGI tree.
> Hope this helps,
> Doug
> --
> ------------------------------------------------------------------------
> Name: kgdb_2.2.14-rh62.diff.gz
> kgdb_2.2.14-rh62.diff.gz Type: unspecified type (APPLICATION/octet-stream)
> Encoding: BASE64

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

This archive was generated by hypermail 2b29 : Sun Apr 30 2000 - 21:00:14 EST