Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 111570

Summary: Threads should be refreshed in a lazy fashion.
Product: [Tools] CDT Reporter: Mohamm <mohammed.naseer>
Component: cdt-debug-cdi-gdbAssignee: cdt-debug-inbox <cdt-debug-inbox>
Status: RESOLVED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3    
Version: 3.0   
Target Milestone: ---   
Hardware: PC   
OS: Linux-GTK   
Whiteboard:

Description Mohamm CLA 2005-10-05 04:22:32 EDT 
Currently threads will refresh with every gdb command. This might be ok for
smaller applications, but when doing for instance kernel debugging, this greatly
slows down the session. 

Doing a simple next command for instance can take about several seconds. This is
because CDT will refresh the thread info with each next and since the kernel has
at any given time various threads active, this inevitably takes a long time.
Comment 1 Nobody - feel free to take it CLA 2006-05-29 15:19:24 EDT 
(In reply to comment #0)
I understand the problem, but we have to refresh threads on every step because there is no notification mechanism in gdb. I don't know any other solution at the moment.
Changing severity to enhancement.
Comment 2 Jonah Graham CLA 2017-10-23 13:41:12 EDT 
(this is part of a batch change)

The CDI debug implementation has been removed in CDT 9.0. Please see bug 484900 and the entry on the New and Noteworthy page https://wiki.eclipse.org/CDT/User/NewIn90#API_modifications