Community
Participate
Working Groups
Make sure that the JVMTI Profiler(s) fully support Java 6 JRE.
Early tests on Windows/IA-32 shows that all profilers (CPU, Heap and Thread) are working fine with the Java SE 6 runtime environment. These are reassuring but not conclusive results. A known issue exists with applications compiled with the Java 6 JDK compiler. These applications are likely to crash under the JVMTI Profiler because our instrumentation engine does not yet fully support the Java 6 new class file format (see Bugzilla 148629).
Status update: the JVMTI Profiler works fine with Java 6 JRE (Windows and Linux, all supported Intel architectures), as long as the Java application itself is *not* compiled with a Java 6 compiler. Note that the Eclipse workbench itself may also have some issues with Java 6. These are not related to the profiler itself and are tracked elsewhere.
Hi Asaf, and others, Can you clarify what the situation is with TPTP 4.4? Without going into my specific Europa + JDK6 circumstances, it might be useful if you updated this bug to say what does and doesn't work in 4.4 Regards, Neale
We tested Applications compiled with Java 5 running in a Java 6 VM without any issues. We do have issues when the code is compiled with Java6.
Status update, applicable for TPTP 4.4 GA: The JVMTI Profiler works well with JRE 6 even with Java 6 class files (class version 50.0), providing that the JRE can "fail over" to the old Java 5 verifier when it encounters an illegal StackMapTable attribute. Luckily, this "fail over" functionality is turned-on by default in most (if not all) Java 6 JREs. The issue of correctly generating the StackMapTable attribute for Java 6 class files is still open.
Please consider for 4.5
Can we close this enhancement since TPTP 4.5 will declare Java 1.6 support and the StackMapAttribute issue will be resolved under 148629?
I think we can.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html).
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.
