[Bug remote/27927] gdb crash with OpenOCD

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

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #14 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Simon Marchi from comment #12)

Looking at the trace:

>   [remote] Sending packet: $qXfer:threads:read::0,1000#92
>   [remote] Packet received: l<?xml version="1.0"?>\n<threads>\n<thread
> id="1">Name: Kernel's Stat Task, State: Delay, Priority: 6</thread>\n<thread
> id="2">Name: Wi-SUN MAC, State: Pend, Priority: 31</thread>\n<thread
> id="3">Name: Wi-SUN Timer Task, State: Pend, Priority: 10</thread>\n<thread
> id="4">Name: Wi-SUN Event Loop Task, State: Pend, Priority:
> 12</thread>\n<thread id="5">Name: Wi-SUN RF Task, State: Pend, Priority:
> 9</thread>\n</threads>\n

This shows the threads, they have id 1-5.

>   [remote] Sending packet: $qC#b4
>   [remote] Packet received: QC0000000000000000

But the remote says that the current thread is 0, which seems
sort of nonsensical.  The docs say:

A THREAD-ID can
also be a literal '-1' to indicate all threads, or '0' to pick any
thread.

However, it seems to me that these special values do not make
sense for a QC response.

IOW, I think this is a bug in the remote stub.

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