[Bug remote/31801] Protocol error: QThreadEvents (thread-events) conflicting enabled

["tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=31801

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW

--- Comment #6 from Tom Tromey <tromey at sourceware dot org> ---
Ok, in this case, gdb is correct to give an error.

What happens is that gdb sends "QThreadEvents+" in its
qSupported packet.  The remote replies "QThreadEvents+",
meaning the packet is supported.

Then later:

&"[remote] Sending packet: $QThreadEvents:1#89\n"
&"[remote] Packet received: \n"

That is, gdb asks for thread events and the remote
replies with the empty response, which means "unsupported" --
but it already said it *is* supported.

This is a bug in the remote.

Now, I do see the empty response documented in the manual.
However, I tend to think this is a cut-and-paste bug
in the manual itself, since the chart in the general
query packets node says:

     Feature Name              Value          Default   Probe
                               Required                 Allowed
...
     ‘QThreadEvents’           No             ‘-’       No

i.e., probing isn't allowed, so the empty response -- IMO --
is nonsensical.

-- 
You are receiving this mail because:
You are on the CC list for the bug.