Serial consoles and remote GDB

[Stephan Uphoff]

Are you sure that your serial line is configured with the
right baud rate?

I also encountered something like this when additional programs
were reading form the serial line and stole characters from gdb.
( terminal emulators for testing, getty? ...)

Your /boot/loader.conf should look somewhat like:

console=comconsole

hint.sio.1.flags=0x80

boot_ddb=1
boot_gdb=1
boot_verbose=1

Good luck
	Stephan


On Sun, 2004-08-29 at 23:19, Rob Deker wrote:
> On Sun, 2004-08-29 at 18:55, Stephan Uphoff wrote:
> > Hi,
> > 
> > Try the patch from kern/65278
> > 
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/65278
> > 
> Thanks,
> 
>  Looks like that did some good (I have my console back now), but when i
> either "boot -g" or break into ddb and give it a "gdb" command, then try
> and connect gdb to it on the other serial port, gdb seems to not be able
> to connect to it (and I consequently have to power cycle the machine to
> un-hang it). What I get from gdb is the following:
> 
> bash-2.05b$ sudo gdb -k kernel.debug
> GNU gdb 5.2.1 (FreeBSD)
> Copyright 2002 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for
> details.
> This GDB was configured as "i386-unknown-freebsd"...
> (kgdb) target remote /dev/cuaa4
> Remote debugging using /dev/cuaa4
> Ignoring packet error, continuing...
> Ignoring packet error, continuing...
> Ignoring packet error, continuing...
> Couldn't establish connection to remote target
> Malformed response to offset query, timeout
> 
> thanks for the help,
> 
> -d