Bugzilla – Full Text Bug Listing
| Summary: | Debug View: Stackframe is not consistently selected on a suspend thread debug event | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Alan Boxall <boxall> |
| Component: | Debug | Assignee: | Platform-Debug-Inbox <platform-debug-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | ||
| Version: | 3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
M6 driver |
I am see my own debug plugin (PDT) and the Java debugger doing the same thing. > if I have a Suspend VM breakpoint nothing is selected when the JVM is suspended. I have to look for the thread that has "... suspended by ... " in its title and expand it to get the stopping stackframe selected< The first time I run a debug session after starting the workbench the stackframe is selected and source and variables appear. If I stop that debug target and start a second debug target it will stop, show the stackframes but the debug target remains selected. The stackframe is not selected and therefore source etc. is not shown. I have confirmed that my suspend events are sent correctly and in the right order. This consistently works in R3.0 In my trace I see that the suspend event is sent from my main thread but my stackframe creation events are sent from a "Worker-n" thread. Could this be a case where the processing of the getStackframes() doesn't finish in time for the thread handling the suspend event to select a stackframe?