Bug#610833: asynchronous command execution is broken in gdb/mi

2011-07-05 Thread Hector Oron
Hello, 2011/7/6 Przemysław Pawełczyk : > I think it cannot be closed without fixing it in squeeze, because > that's the point of debian stable (and I presumably wouldn't lost my > time back then for squeeze greatness knowing I will be asked such > question). This bug makes use of async commands (

Bug#610833: asynchronous command execution is broken in gdb/mi

2011-07-05 Thread Przemysław Pawełczyk
Hello Hector! Thank you for finding time to look at this issue after half year (in 6.0.2 era). I have already given up my hope, so seeing notification about your reply was reassuring, but I cannot tell the same thing about its content. On Tue, Jul 5, 2011 at 22:54, Hector Oron wrote: > On Sun, J

Bug#610833: asynchronous command execution is broken in gdb/mi

2011-07-05 Thread Hector Oron
Hello, On Sun, Jan 23, 2011 at 03:43:29AM +0100, Przemysław Pawełczyk wrote: > Package: gdb > Version: 7.0.1-2+b1 > Severity: normal > Tags: patch > Now I can say that it's broken, but finding out that gdb is the culprit, > whether it was fixed already in newer versions and when exactly took me

Bug#610833: asynchronous command execution is broken in gdb/mi

2011-01-22 Thread Przemysław 'Przemoc' Pawełczyk
> * How I can see it myself? > > Almost real-world example: > >  $ qemu -hda /path/to/linux-0.2.img -s  # [1] >              # wait at least until kernel is loaded >  $ gdb       # we'll mimic some Qt Creator actions here Sorry, obviously here should be this instead: $ gdb -i mi >            

Bug#610833: asynchronous command execution is broken in gdb/mi

2011-01-22 Thread Przemysław Pawełczyk
Package: gdb Version: 7.0.1-2+b1 Severity: normal Tags: patch * Preface gdb/mi is a line based machine oriented text interface to gdb. Used primarily by programs wishing to use gdb as a backend for a debugger GUI or an IDE. Notable example is the Qt Creator. Frontend may specify a preference fo