top mode. GDB can not send any other command to the
stub until the stub returns a stop reply to the first 's'. Remember,
there's no vStopped+notifications in the all-stop mode protocol.
--
Pedro Alves
On Wednesday 06 October 2010 18:19:53, Oleg Nesterov wrote:
> On 10/05, Pedro Alves wrote:
> > "The stub must support @samp{vCont} if it reports support for
> > multiprocess extensions (@pxref{multiprocess extensions})."
>
> Cough. Previously I was told here (on a
On Tuesday 05 October 2010 19:30:38, Pedro Alves wrote:
> Now, given this, I won't be surprised if you're seeing races
> with ->s, <-OK, ->vCont sequences, as GDB may well be thinking
> that the "OK" is a reply to the vCont.
>
I meant ->s, <-OK, ->vStopped sequences.
--
Pedro Alves
mote_console_output
happens to just bail out silently.
Now, given this, I won't be surprised if you're seeing races
with ->s, <-OK, ->vCont sequences, as GDB may well be thinking
that the "OK" is a reply to the vCont.
> So, I strongly believe gdb is buggy and should be fixed.
Fix your stub to implement vCont;s/c(/S/C).
--
Pedro Alves
