JDK-6346964 : Support dynamic enabling of extended DTrace probes
- Type: Enhancement
- Component: core-svc
- Sub-Component: tools
- Affected Version: 5.0
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2005-11-07
- Updated: 2010-08-24
- Resolved: 2006-04-19
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 6 |
|---|
6 b80Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
method-entry/return, object-alloc, and monitor-entry/exit probes are disabled by fault in the Mustang VM. The users are required to set -XX:+ExtendedDTraceProbes at startup time so that these probes can be enabled by DTrace at runtime. One most important and powerful feature DTrace provides is the ability to trace applications without requiring it to restart (with special flags). So we should fix this so that these probes can be turned on any time.
Comments
|