| Summary: | Deadlock in main and debug threads | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Omry Yadan <public> | ||||
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | darin.eclipse | ||||
| Version: | 3.1 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Omry Yadan
Created attachment 32649 [details]
Thread dump during deadlock
Could you confirm the version of Eclipse you are using (it might be older than 3.1?). The deadlock is caused by a non-ui thread attempting to prompt for source where a breakpoint was hit waiting for the UI thread with a lock on the thread (and source could not be found), and the UI thread already performing a source lookup, needing a lock on the thread. The source locator being used has been deprecated since 3.0. If you were to re-create your launch configuration being used, you should get the new source locator. I am pretty sure about the eclispe version. I`ll give you a definitive answer tommorow. A possible cause can be sysdeo tomcat plugin. I have only saw it while debugging tomcat which ras ran by it (so far). This is the eclipse build I am using: Version: 3.1.0 Build id: I20050627-1435 OK, Sysdeo is using a depreacted source locator then. There still may be issues we want to fix in the Java debugger here (i.e. we hold a lock while notifying clients of a breakpoints, and a listener may decided to prompt the user). Deferred Closing. No intention to fix deprecated source locator. As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you. |