Bug 159443 - Avoid usage of "info thread" gdb CLI command
Summary: Avoid usage of "info thread" gdb CLI command
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: 3.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL: http://dev.eclipse.org/mhonarc/lists/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-02 07:42 EDT by Denis PILAT CLA
Modified: 2020-09-04 15:17 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Denis PILAT CLA 2006-10-02 07:42:26 EDT 
Today Eclipse could become unsable when debugging a program on a remote board.
"Info thread" cli command takes arround 7 sec to execute,  and it is executed at each step, plus some other command and that take an overall time of 9 seconds.
This case occures when debugging a program with a large number of threads.

We propose to use the mi command -thread-list-ids and take the current thread information from the stop reply packet.

Other GDB commands -info-thread and -thread-list-all-threads are going to be implemented in GDB but won't be available before gdb6.6 release.

See below link for more details.
http://dev.eclipse.org/mhonarc/lists/cdt-debug-dev/msg01525.html

GDB thread discussion here:
http://sources.redhat.com/ml/gdb/2006-09/msg00178.html