If I am debugging some multithreaded Java code in Eclipse - with a main class RunTest, and an interesting class QueueListener.
Assumptions:
When debugging in Eclipse - both breakpoints come up. But Eclipse gives priority to RunTest - and I have to manually flip it over to the QueueListener by selecting that thread in the debugger - and keep repeating this over and over.
Is there a way to tell Eclipse that I'm more interested in the QueueListener, and consider the testrunner to be a lower priority - when it chooses debug breakpoints to show?
You can fix this immediately by opening the Markers view and delete the Java Exception Breakpoints. However, to permanently remove this type of breakpoints, you have to go to the Java Debug options and uncheck the "Suspend excecution on uncaught exceptions" option.
To define a breakpoint in your source code, right-click in the left margin in the Java editor and select Toggle Breakpoint. Alternatively, you can double-click on this position. The Breakpoints view allows you to delete and deactivate Breakpoints and modify their properties.
The solution was to enable it again, start a debug session, the breakpoint is hit and shown in the UI, then disable again the option. There is also another simpler way that will make Eclipse show the debugging highlight at the breakpoint or rather refresh the debugging UI to work as it should.
The answer can be found in the eclipse source code within the ThreadEventHandler
method. There is a queue of suspended threads, as below:
/**
* Queue of suspended threads to choose from when needing
* to select a thread when another is resumed. Threads
* are added in the order they suspend.
*/
private Set fThreadQueue = new LinkedHashSet();
Further down, every time a breakpoint is hit, the suspended thread is added to this queue:
protected void handleSuspend(DebugEvent event) {
...
queueSuspendedThread(event);
...
}
The method to get the next suspended thread is:
protected synchronized IThread getNextSuspendedThread() {
if (!fThreadQueue.isEmpty()) {
return (IThread) fThreadQueue.iterator().next();
}
return null;
}
So the answer is no, there is no control over the order, it will strictly be in the order that each thread hits the breakpoint and is added to the underlying queue.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With