-
Enhancement
-
Resolution: Fixed
-
P4
-
hs18
-
b01
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2193330 | 7 | Christian Thalinger | P4 | Closed | Fixed | b94 |
| JDK-2197892 | 6u23 | Christian Thalinger | P4 | Closed | Fixed | b01 |
| JDK-2199793 | 6u22m | Christian Thalinger | P4 | Closed | Fixed | b01 |
| JDK-2197601 | 6u21p | Christian Thalinger | P4 | Closed | Fixed | b03 |
Gary Benson wrote:
Hi all,
Zero needs a couple of new methods to allow Shark to access the new
frame anchor field JavaFrameAnchor::_last_Java_fp that was added by
6939182. It also needs a method to allow Shark's fake stub frames
to be identified from within the frame walker. This webrev adds
them:
http://cr.openjdk.java.net/~gbenson/shark-api-updates/
I don't have a bug id for this.
Cheers,
Gary
Hi all,
Zero needs a couple of new methods to allow Shark to access the new
frame anchor field JavaFrameAnchor::_last_Java_fp that was added by
6939182. It also needs a method to allow Shark's fake stub frames
to be identified from within the frame walker. This webrev adds
them:
http://cr.openjdk.java.net/~gbenson/shark-api-updates/
I don't have a bug id for this.
Cheers,
Gary
- backported by
-
JDK-2193330 Zero/Shark interface updates
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
JDK-6962193 Rebrand some Zero files
-
- Resolved
-