Community
Participate
Working Groups
For GDB < 7.0, we use the class CLIEventProcessor which triggers the ThreadCreate event based on CLI printouts. The threadId used is a simple counter starting from 0 (fLastThreadId). When we restart the application, this threadId should be reset to 0.
Created attachment 168951 [details] Fix Simple solution that avoids new APIs. Committed to HEAD.
John, can you review?
*** cdt cvs genie on behalf of mkhouzam *** Bug 313372: Re-create the CLIEventProcessor when we restart the program, so as to reset the internal threadId count. [*] GDBControl.java 1.15 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/gdb/service/command/GDBControl.java?root=Tools_Project&r1=1.14&r2=1.15