Hi,
I think the main problem here is not only that compiled code uses the
frame pointer as a general purpose register, but the fact that even
the VM itself currently can not reliably take a stack trace of a
thread at any arbitrary PC. An external sampling profiler like perf
can interrupt the VM at
Greetings,
Kindly asking for reviews for the following changeset.
Bug: https://bugs.openjdk.java.net/browse/JDK-8056049
Webrev: http://cr.openjdk.java.net/~mgronlun/8056049/webrev01/
Description:
The issue is Windows specific. And the problem relates to using the
Performance Da
Hi Brendan,
We are working with the Solaris on prototyping an assisted approach to
resolve the issue.
In this approach the jhelper.d (the dtrace jstack action provider on VM
side) is assisting
the DTrace framework to do the stack walking cooperatively.
I've assigned the bug JDK-6617153 to mys
