On Wed, 21 Oct 2026 02:26:26 GMT, Yasumasa Suenaga <[email protected]> wrote:
>> Valhalla introduced flattened value object, however SA cannot dump it into
>> heapdump e.g. `jhsdb jmap --binaryheap`.
>> Actually HeapHprofBinWriter.java has following lines. Hence the user cannot
>> check flattened object from heapdump generated by SA.
>>
>>
>> case JVM_SIGNATURE_CLASS:
>> case JVM_SIGNATURE_ARRAY: {
>> if (field.isFlat()) {
>> // FIXME - we don't handle flattened fields yet. Just treat
>> them
>> // as a null reference. See JDK-8381370.
>> writeObjectID(null);
>>
>>
>> This PR addressed it.
>>
>> ---------
>> - [x] I confirm that I make this contribution in accordance with the
>> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai).
>
> Yasumasa Suenaga has updated the pull request with a new target base due to a
> merge or a rebase. The incremental webrev excludes the unrelated changes
> brought in by the merge/rebase. The pull request contains four additional
> commits since the last revision:
>
> - Re-enable HeapDumpTestWithActiveProcess.java
> - Merge branch 'master' into JDK-8381370
> - Use getFieldHolder() rather than getKlass()
> - 8381370: SA is not writing out flattened fields to the hprof file
@plummercj
[JDK-8381370](https://bugs.openjdk.org/browse/JDK-8381370) is focusing on hprof
file, in other words GXL can be treated in another issue. So can I exclude
change for GXL from this PR?
-------------
PR Comment: https://git.openjdk.org/jdk/pull/33395#issuecomment-6331311797
