Bug 24177 - RSP Remote Protocol documentation for vCont is unclear
Summary: RSP Remote Protocol documentation for vCont is unclear
Status: UNCONFIRMED
Alias: None
Product: gdb
Classification: Unclassified
Component: web (show other bugs)
Version: HEAD
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-06 01:41 UTC by Lucien Murray-Pitts
Modified: 2019-02-06 01:41 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lucien Murray-Pitts 2019-02-06 01:41:32 UTC 
Whilst working on QEMU's gdbstub we ran across an area of confusion with the vCont packet.
( see mail archive discussion: http://lists.nongnu.org/archive/html/qemu-devel/2019-02/msg01121.html )

The crux of this discussion is that vCont in a multi-process environment allows for the packet "vCont;c" (no pid/tid descriptor).  However this is at odds with the description for the vcont packet with no tid/pid AND the thread-id description.

From Vcont documents online:
( https://sourceware.org/gdb/current/onlinedocs/gdb/Packets.html#vCont-packet )
> For each inferior thread, the leftmost action with a matching thread-id 
> is applied. .... An action with no thread-id matches all threads.

The problem here is we don't know which process to act on.

Could we have some clarity on expected behavior in the online RSP document please.