Community
Participate
Working Groups
The goal is to decrease turnaround time and debug effort for profiling/piAgent bugs (especially hangs and crashes). The primary means would be a controllable level of debug trace that would record piAgent operation including initialization, heap dump (collect obj refs), and internal (eg: hash table, storage, etc) events. JVMPI and RAC interactions would also be recorded. A secondary means would be to create a minimal standalone stress application and piAgent version to facilitate submission and resolution of JVM bugs (which are sometimes the root cause of profiling problems).
Retargeted as per yesterday's Platform call.
PMC approved deferral from 4.2 plan on Feb 7th.
No plan to fix
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.