Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Feb 2020 16:13:57 +0100
From:      Andrea Venturoli <ml@netfence.it>
To:        freebsd-questions@freebsd.org
Subject:   Re: Cannot get remote GDB to work
Message-ID:  <6cabc27a-81c2-3735-fa24-6f573667211d@netfence.it>
In-Reply-To: <50a10abf-4873-2acc-4f8b-efb9bddb1194@netfence.it>
References:  <50a10abf-4873-2acc-4f8b-efb9bddb1194@netfence.it>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 2020-02-11 15:09, Andrea Venturoli wrote:
> Hello.
> 
> I'm trying to debug through a serial cable, as described in:
>> https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-online-gdb.html 
>>
> 
> I followed the instruction (I believe correctly), but when I issue 
> "target remote /dev/cuau0", I get:
> 
>> Remote debugging using /dev/cuau0
>> Ignoring packet error, continuing...
>> warning: unrecognized item "timeout" in "qSupported" response
>> Ignoring packet error, continuing...
>> Remote replied unexpectedly to 'vMustReplyEmpty': timeout
> 
> 
> 
> I tried launching "cu -l /dev/cuau0" on both sides: I can correctly see 
> what I type in the debugging terminal appear on the host's screen, but 
> not vice versa.
> This starts working again, when I remove flags 0x80 from 
> hint.uart.0.flags and change it back to 0x10 (default).
> 
> 
> Any hint?
> 
>   bye & Thanks
>      av.
> 
> P.S. Both machines are physical (no virtualization here), both are 
> 12.1/amd64 and both serial ports are dumb old style serial ports.

Sorry, I hate to bump.

If no one can help here, can you suggest somewhere else to take this 
question?

  bye & Thanks
	av.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?6cabc27a-81c2-3735-fa24-6f573667211d>