RFR: 8276209: Some call sites doesn't pass the parameter 'size' to SharedRuntime::dtrace_object_alloc(_base) [v2]

Denghui Dong ddong at openjdk.java.net
Mon Nov 8 01:26:37 UTC 2021


On Sun, 31 Oct 2021 22:56:44 GMT, Denghui Dong <ddong at openjdk.org> wrote:

>> Hi,
>> 
>> Could I have a review of this fix that corrects the oop size value of dtrace_object_alloc(_base).
>> 
>> JDK-8039904 added a new parameter 'size' to SharedRuntime::dtrace_object_alloc and dtrace_object_alloc_base, but didn't modified the callsites(interpreter/c1/c2).
>> 
>> To make this fix as simple as possible, I overloaded dtrace_object_alloc_base rather than dtrace_object_alloc.
>> 
>> Thanks,
>> Denghui
>
> Denghui Dong has updated the pull request incrementally with one additional commit since the last revision:
> 
>   fix build problem

Gentle ping?
This problem seems to have existed for a long time. I think it's because there are few users, so it's not reported
As far as I know, a BCC's tool relies on this probe.
https://github.com/iovisor/bcc/blob/master/tools/lib/uobjnew.py#L110

-------------

PR: https://git.openjdk.java.net/jdk/pull/6181


More information about the serviceability-dev mailing list