From c91d7e25fd9b50c70c26be54bd0d625c4179a2a9 Mon Sep 17 00:00:00 2001 From: pst Date: Wed, 4 Jun 1997 16:44:29 +0000 Subject: Document a non-standard gdbremote protocol extension (kludge, really) that I snuck in to our GDB last year. This allows you to debug headless machines by sharing the console port between the debugger and the system console. It's not 100% reliabile, but it works well. It's optional and disabled by default. Submitted by: Juniper Networks --- sys/conf/NOTES | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) (limited to 'sys/conf/NOTES') diff --git a/sys/conf/NOTES b/sys/conf/NOTES index e4ba034..2202011 100644 --- a/sys/conf/NOTES +++ b/sys/conf/NOTES @@ -2,7 +2,7 @@ # LINT -- config file for checking all the sources, tries to pull in # as much of the source tree as it can. # -# $Id: LINT,v 1.341 1997/06/04 04:55:26 pst Exp $ +# $Id: LINT,v 1.342 1997/06/04 16:25:05 pst Exp $ # # NB: You probably don't want to try running a kernel built from this # file. Instead, you should start from GENERIC, and add options from @@ -256,6 +256,15 @@ options DDB # options DDB_UNATTENDED +# +# If using GDB remote mode to debug the kernel, there's a non-standard +# extension to the remote protocol that can be used to use the serial +# port as both the debugging port and the system console. It's non- +# standard and you're on your own if you enable it. See also the +# "remotechat" variables in the FreeBSD specific version of gdb. +# +options GDB_REMOTE_CHAT + # # KTRACE enables the system-call tracing facility ktrace(2). # -- cgit v1.1