Re: BUG: gdb && notification packets (Was: gdbstub initial code, v12)

2010-10-05 Thread Pedro Alves
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

Re: BUG: gdb && notification packets (Was: gdbstub initial code, v12)

2010-10-05 Thread Pedro Alves
On Tuesday 05 October 2010 18:27:29, Oleg Nesterov wrote: > The more or less "typical" transcript is: > > [... snip ...] > => s This is already wrong. "The stub must support @samp{vCont} if it reports support for multiprocess extensions (@pxref{multiprocess extensions})." The stub

BUG: gdb && notification packets (Was: gdbstub initial code, v12)

2010-10-05 Thread Oleg Nesterov
On 10/04, Oleg Nesterov wrote: > > While trying to understand what does this mean, I hit another bug > in ugdb. No, /usr/bin/gdb is buggy. > A multithreaded tracee can "hang" if gdb simulates > watchpoints with single-steps + mem-fetch/compare. It doesn't, but gdb "forgets" about the pending "St