RE: Remote Serial Protocol -- reply to '?' when target running

["taylor, david" <david.taylor@emc.com>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1299 bytes --]


> From: Michael Eager [mailto:eager@eagerm.com]
> Sent: Tuesday, August 09, 2016 3:08 PM
> To: taylor, david; gdb@sourceware.org
> Subject: Re: Remote Serial Protocol -- reply to '?' when target running
> 
> On 08/09/2016 11:40 AM, taylor, david wrote:
> >> From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org]
> On
> >> Behalf Of Michael Eager

> The JTAG pod I'm using does not respond with "QNonStop+" in response
> to "qSupported".  Perhaps it should.

Our stub sets it and I also do 'set non-stop on' in my .gdbinit file.  The entry in
my .gdbinit might predate the stub returning it, I don't recall.

> The JTAG pod does respond to '?' with OK.  After a few other exchanges,
> gdb goes into a wait, waiting to receive something from the target.
> 
> What do you do?  Send a stop reply packet when the target stops?

Our target typically has 80-110 threads when I connect.
We support asynchronous notifications as well.

When GDB connects to the target, a thread is created to service GDB.
If multiple GDB's connect, multiple threads get created -- each dedicated
to a specific GDB.

There's also a networking thread and a bunch of other threads.

Our target never stops.  Individual threads?  Yes.  The target as a whole?  No.
\x16º&ÖëzÛ«ŸŽvשb²Ö«r\x18\x1d