-
Bug
-
Resolution: Fixed
-
P3
-
hs18
-
b04
-
sparc
-
solaris_9
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2192537 | 7 | Tom Rodriguez | P3 | Closed | Fixed | b92 |
JDK-2198017 | 6u23 | Tom Rodriguez | P3 | Resolved | Fixed | b01 |
JDK-2199969 | 6u22m | Tom Rodriguez | P3 | Resolved | Fixed | b01 |
JDK-2193562 | 6u21p | Tom Rodriguez | P3 | Resolved | Fixed | b03 |
The set of always on capabilities include thing which will cause changes in the code the compiler generates which interferes with using JVMTI to support profiling since you aren't profiling the code you would really be executing. In particular this piece of code should change.
JvmtiExport::set_can_access_local_variables(
avail.can_access_local_variables ||
avail.can_redefine_classes ||
avail.can_retransform_classes);
JvmtiExport::set_can_access_local_variables(
avail.can_access_local_variables ||
avail.can_redefine_classes ||
avail.can_retransform_classes);
- backported by
-
JDK-2193562 JVMTI always on capabilities change code generation too much
-
- Resolved
-
-
JDK-2198017 JVMTI always on capabilities change code generation too much
-
- Resolved
-
-
JDK-2199969 JVMTI always on capabilities change code generation too much
-
- Resolved
-
-
JDK-2192537 JVMTI always on capabilities change code generation too much
-
- Closed
-
- relates to
-
JDK-6885609 java -client -XX:-JavaMonitorsInStackTrace cause
-
- Closed
-
-
JDK-7050591 capabilities in init_onload_capabilities() need to be revisited
-
- Closed
-
(1 relates to)