Community
Participate
Working Groups
The JVMTI attach use case will need to be enabled once the relevant blocking defects are resolved. See the defects that blocks this top-level defect.
To enable the attach use case, the following block needs to be uncommented in plugin.xml file of the JVMTI plug-in: <association launchConfigID = "org.eclipse.hyades.trace.ui.internal.launcher.localJavaProcess"> <mechanism mechanismID = "org.eclipse.tptp.trace.jvmti.jvmtiMechanism"> <configuration launchDelegate = "org.eclipse.tptp.platform.jvmti.client.internal.launcher.TIAttachLauncherDelegate" configurationId = "org.eclipse.tptp.trace.jvmti.tiConfiguration" associatedAgent = "org.eclipse.tptp.platform.jvmti.TIAgent"> </configuration> </mechanism> </association>
Ali, The attach use case is working for all the use cases but the Eclipse workbench and OSGI profiling. I am leaving this defect open to get the final fix. But the current state should enable the end to end testing.
I'm taking over this defect. Guru, please don't check-in anything under this defect.
Guru, My one month commitment to TPTP is over and I'm switching back to COSMOS. I'm re-assigning this defect back to you. I'm not in favor of checking in any more code into i3 at this point. I would recommend delaying this defect to either i4 or the next release. I don't think that this function can be made stable in i3's time-frame.
What else is pending to be done but for the issue in 182189? I am going to Ping the AC team again on the defect 182189
Adding a dependency on Bug 190684, which addresses the detection of the active JVMTI Data collector.
Right now attaching to a remote agent (I have only tried EM64T) will cause the Profile launch configuration Dialog to freeze and thereby freeze the workbench. Plese investigate as a test case for this defect as well and/or let me know if you would prefer I open a separate defect for that issue.
This is caused due to the a partial check in of 182200. The check in has hence been completed and can be tested by using Code of CVS.
The (In reply to comment #8) > This is caused due to the a partial check in of 182200. > The check in has hence been completed and can be tested by using Code of CVS. The check-in was not completed. I checked the source code today and the method org.eclipse.tptp.platform.jvmti.client.internal.launcher.TIAnalysisTypeFiltration.include (as described in Bug 190684) is not fully implemented. It still has the TODO comment left by Ali, as described in comment 20 of bug 182200).
190684 has addressed the analysis type filtration. The pending case in the attach is in 186807 - the data processor is not replaced during attach.
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.
