On 08/03, Kevin Buettner wrote:
On Tue, 3 Aug 2010 15:14:36 +0200
Oleg Nesterov o...@redhat.com wrote:
To avoid the unnecessary details, consider the oversimplified example,
$ sleep 1
[1] 2923
$ cat SLEEP
set target-async on
set non-stop
target
On Wed, 4 Aug 2010 21:39:35 +0200
Oleg Nesterov o...@redhat.com wrote:
I'd be curious to know if the behavior improves when you omit
set target-async on and set non-stop.
Yes, it works without target-async ;)
I think that using set target-async on is probably very buggy as it
is not used
On 08/03, Jan Kratochvil wrote:
On Wed, 28 Jul 2010 20:17:02 +0200, Oleg Nesterov wrote:
Btw, gdb crashes very often right after
(gdb) set target-async on
(gdb) set non-stop
(gdb) file mt-program
(gdb) target extended-remote :port
(gdb) attach its_pid
I
Forgot to mention,
On 08/03, Oleg Nesterov wrote:
So I assumed it is always safe to resend the notification unless gdb already
sent vStopped. Since it is not clear to me when it makes sense to resend it,
currently gdbstub does re-send every time /proc/ugdb reports the new event
(T00 in this
On Tue, 3 Aug 2010 15:14:36 +0200
Oleg Nesterov o...@redhat.com wrote:
To avoid the unnecessary details, consider the oversimplified example,
$ sleep 1
[1] 2923
$ cat SLEEP
set target-async on
set non-stop
target extended-remote :2000
