RFR: 8246434: Threads::print_on_error assumes that the heap has been set up
Stefan Karlsson
stefan.karlsson at oracle.com
Wed Jun 3 11:51:27 UTC 2020
Thanks, David.
StefanK
On 2020-06-03 13:37, David Holmes wrote:
> Looks good and trivial.
>
> Thanks,
> David
>
> On 3/06/2020 8:24 pm, Stefan Karlsson wrote:
>> Hi all,
>>
>> Please review this trivial patch to null check the access to the
>> heap, when printing threads to the hs_err files.
>>
>> https://cr.openjdk.java.net/~stefank/8246434/webrev.01
>> https://bugs.openjdk.java.net/browse/JDK-8246434
>>
>> Output from an initialization crash without this fix:
>> ---
>> Other Threads:
>>
>> [error occurred during error reporting (printing all threads), id
>> 0xb, SIGSEGV (0xb) at pc=0x0000000104cbb609]
>> ---
>>
>> with the fix:
>> ---
>> Other Threads:
>>
>> =>0x00007ff10980e220 (exited) JavaThread "Unknown thread"
>> [_thread_in_vm, id=7171, stack(0x00007000083dc000,0x00007000084dc000)]
>> ---
>>
>> Thanks,
>> StefanK
More information about the hotspot-dev
mailing list