Re: [PATCH] gdbstub: Correct misparsing of vCont C/S requests

2020-12-11 Thread Alex Bennée
Peter Maydell writes: > On Mon, 23 Nov 2020 at 13:41, Alex Bennée wrote: >> >> >> Peter Maydell writes: >> >> > In the vCont packet, two of the command actions (C and S) take an >> > argument specifying the signal to be sent to the process/thread, which is >> > sent as an ASCII string of two

Re: [PATCH] gdbstub: Correct misparsing of vCont C/S requests

2020-12-11 Thread Peter Maydell
On Mon, 23 Nov 2020 at 13:41, Alex Bennée wrote: > > > Peter Maydell writes: > > > In the vCont packet, two of the command actions (C and S) take an > > argument specifying the signal to be sent to the process/thread, which is > > sent as an ASCII string of two hex digits which immediately follow

Re: [PATCH] gdbstub: Correct misparsing of vCont C/S requests

2020-11-23 Thread Alex Bennée
Peter Maydell writes: > In the vCont packet, two of the command actions (C and S) take an > argument specifying the signal to be sent to the process/thread, which is > sent as an ASCII string of two hex digits which immediately follow the > 'C' or 'S' character. > > Our code for parsing this pa

Re: [PATCH] gdbstub: Correct misparsing of vCont C/S requests

2020-11-23 Thread Philippe Mathieu-Daudé
On 11/21/20 10:03 PM, Peter Maydell wrote: > In the vCont packet, two of the command actions (C and S) take an > argument specifying the signal to be sent to the process/thread, which is > sent as an ASCII string of two hex digits which immediately follow the > 'C' or 'S' character. > > Our code f

[PATCH] gdbstub: Correct misparsing of vCont C/S requests

2020-11-21 Thread Peter Maydell
In the vCont packet, two of the command actions (C and S) take an argument specifying the signal to be sent to the process/thread, which is sent as an ASCII string of two hex digits which immediately follow the 'C' or 'S' character. Our code for parsing this packet accidentally skipped the first o