Date: Thu, 24 Apr 1997 12:25:58 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: Pavlin Ivanov Radoslavov <pavlin@catarina.usc.edu> Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel remote debugging using gdb Message-ID: <Pine.BSF.3.95q.970424121921.536A-100000@herring.nlsystems.com> In-Reply-To: <199704240118.SAA05346@catarina.usc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 23 Apr 1997, Pavlin Ivanov Radoslavov wrote: > I need to do remote debugging of the kernel, but I am using the > first serial port as a serial console. How can I specify/change the > target machine to use the second serial port for remote debugging > purpose? Changing CONADDR and CONUNIT will affect the serial console > too, right? In current, you ought to be able to have: device sio0 at isa? port "IO_COM1" tty irq 4 flags 0x10 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 flags 0x50 vector siointr This would specify that sio0 is the 'high level' console for printfs etc. and sio1 is the 'low level' console for gdb. Unfortunately it wont work since sio doesn't understand how to have two consoles, one high level and one low level. It would be a small amount of work to teach sio.c and i386-gdbstub.c about this situation. A handy project for you... -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.970424121921.536A-100000>