AsyncGetCallTrace java profiling
Staffan Larsen
staffan.larsen at oracle.com
Mon Aug 26 04:30:08 PDT 2013
I think this is your bug report: http://bugs.sun.com/view_bug.do?bug_id=8022893
I have updated Affected Versions to include 8 as well. The change will take a day or so to propagate.
/Staffan
On 26 aug 2013, at 12:08, Alexandre De Champeaux <adc at quartetfs.com> wrote:
> Hi,
>
> I was able to reproduce the bug running java 8 (build b103, and so hotspot build 25.0-b45). So I would like to update the bug report to java 8. I don't have access to it though. Should I post a new one?
>
>
> On Tue, Aug 13, 2013 at 2:13 PM, Alexandre De Champeaux <adc at quartetfs.com> wrote:
> Ok thanks. I just posted a bug report to bugs.sun.com describing the issue (id 9005974).
>
>
> On Tue, Aug 13, 2013 at 1:00 PM, Alan Bateman <Alan.Bateman at oracle.com> wrote:
> On 13/08/2013 09:11, Alexandre De Champeaux wrote:
>>
>> Hi all,
>>
>> I posted this message a few days ago in the discuss mailing list. This one seems way more accurate though, so i am posting it again.
>>
>> Following his blog post (http://jeremymanson.blogspot.fr/2013/07/lightweight-asynchronous-sampling.html), I have been trying to use the code Jeremy Manson proposes to use the AsyncGetCallTrace function.
>> Although it works smoothly on small examples, I see some impossible stacktraces on real world projects, with complex interface structures. I have posted a bug report that reproduces it and gives more details here : https://code.google.com/p/lightweight-java-profiler/issues/detail?id=1
>>
>> I am trying to estimate if those stacktraces are sparse (seems to be so), and so if a profiler that uses this feature will be reliable.
>>
>> Any known bugs / limitations of the AsyncGetCallTrace function?
>> This function being undocumented, in what extent does it stays up to date?
>>
>> Thanks for your answers
>>
>> Alex
> When you say you've posted a bug report, does this mean to bugs.sun.com? While not technically supported, it is known to be used by some products so if there is an issue (and I remember this had a long bug tail originally) then it would be good to track it.
>
> -Alan.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/serviceability-dev/attachments/20130826/441c356e/attachment.html
More information about the serviceability-dev
mailing list