Bugzilla – Full Text Bug Listing
| Summary: | Deadlock detection doesn't work at Thread Analysis | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Alexander N. Alexeev <analexee> | ||||||||
| Component: | TPTP | Assignee: | Alexander N. Alexeev <analexee> | ||||||||
| Status: | CLOSED FIXED | QA Contact: | |||||||||
| Severity: | enhancement | ||||||||||
| Priority: | P1 | CC: | analexee, ewchan, sluiman | ||||||||
| Version: | unspecified | Keywords: | plan | ||||||||
| Target Milestone: | --- | ||||||||||
| Hardware: | All | ||||||||||
| OS: | All | ||||||||||
| Whiteboard: | closed460 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Alexander N. Alexeev
Created attachment 74046 [details]
Application with deadlock
This sounds major/critical to me. If the problem is as large as the description, this does seem like a stop ship defect. This is an enh. to leverage the Model capabilities to enable deadlock detection. When the 4.5 stream is open this will be requested as a candidate. Seems problem is in the model (Loader of monContendedEnter event) All deadlock analysis is doing during "monContendedEnter" event loading, but even for simplest application it isn't able to detect deadlock. JVMTI agent sends all required events with appropriated data. Can we change component to "Platform.model"? I've spent some time for investigation and propose a patch. Harm, please, take a look on it. Thanks, Alex. Created attachment 82062 [details]
Patch
Created attachment 82063 [details]
Test application
(In reply to comment #5) > Seems problem is in the model (Loader of monContendedEnter event) > All deadlock analysis is doing during "monContendedEnter" event loading, but > even for simplest application it isn't able to detect deadlock. > JVMTI agent sends all required events with appropriated data. > > Can we change component to "Platform.model"? > > I've spent some time for investigation and propose a patch. > Harm, please, take a look on it. > > Thanks, Alex. > I will get to this asap Patch in Comment #6 is submitted to HEAD (4.5). Please change the target to the 4.5 iteration when this Bugzilla was resolved. As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. |