[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-debug-dev] multi-threaded programs and GDB interface
|
> From: cdt-debug-dev-bounces@xxxxxxxxxxx [mailto:cdt-debug-dev-
> bounces@xxxxxxxxxxx] On Behalf Of Denis PILAT
> Sent: Monday, September 25, 2006 10:36 AM
> To: CDT Debug developers list
> Subject: Re: [cdt-debug-dev] multi-threaded programs and GDB interface
>
> I've just checked in JAVA sources, and the current thread
> is effectively read from the output od "info threads" command.
> I'll submit an enh. request for that.
>
A few more things, about "info threads" vs "thread-list-ids"
(1) thread-list-ids was crashing on some version of GDB, it was corrected by
now, but since the mandate of the CDT/Debug was to run since 5.2.1 we felt
more comfortable to stick with it.
(2) The other point is synchronization of the IDE vs a command line.
Although we could retrieve the thread id in the async "*stopped," a user
could change the active thread and -thread-list-ids did not list the active
thread.
(3) Some folks use the output of the "info threads" to extract more
information like thread name and other goodies that can be use within the
IDE.
(1) is no longer a show stopper, IMHO. Having -thread-info and
-thread-list-ids printing the info values when passing an argument is big +.
IMHO.
