MI: "^running" issues

[Nick Roberts]

 > > There may be other cases I can't remember now. But I'd surely
 > > welcome a multithreaded gdb. gdb is needed for many cases, not
 > > just a local program on a linux box.
 > 
 > Nothing that you can't solve with non-blocking IO.
 > 
 > Debugging multi-threaded code is bad enough in itself.  You don't need
 > to make matters worse by making gdb itself less deterministic.

Perhaps Fabian is assuming that asynchronus operation requires a multithreaded
gdb.  The async branch that I created was multi-threaded but the patch that I
currently have (under Daniel's guidance) and which I've previously posted to
the gdb-patches mailing list:

http://sourceware.org/ml/gdb-patches/2006-11/msg00225.html

and briefly described in:

http://sourceware.org/ml/gdb-patches/2007-06/msg00315.html

is not.

-- 
Nick                                           http://www.inet.net.nz/~nickrob