RFR(xxs): 8144702: Using tid decorator in Unified Logging may crash VM

Thomas Stüfe thomas.stuefe at gmail.com
Sat Dec 5 06:22:22 UTC 2015


Thanks Coleen!



On Fri, Dec 4, 2015 at 4:54 PM, Coleen Phillimore <
coleen.phillimore at oracle.com> wrote:

>
> This looks good.
> Coleen
>
>
> On 12/4/15 7:45 AM, Thomas Stüfe wrote:
>
>> Thanks, Markus!
>>
>> On Fri, Dec 4, 2015 at 1:12 PM, Marcus Larsson <marcus.larsson at oracle.com
>> >
>> wrote:
>>
>> Hi Thomas,
>>>
>>>
>>> On 2015-12-04 13:05, Thomas Stüfe wrote:
>>>
>>> Hi all,
>>>>
>>>> please review this tiny fix:
>>>>
>>>> webrev:
>>>>
>>>>
>>>> http://cr.openjdk.java.net/~stuefe/webrevs/8144702-Using-tid-decorator-in-Unified-Logging-may-crash-VM/webrev.00/webrev/
>>>> bug: https://bugs.openjdk.java.net/browse/JDK-8144702
>>>>
>>>> Looks good. Thanks for fixing this!
>>>
>>> Regards,
>>> Marcus
>>>
>>>
>>>
>>> Unified Logging uses Thread::current() when printing out the "tid"
>>>> decorator, which will crash the VM if logging is done after thread start
>>>> and before thread TLS slot initialization or after thread TLS slot
>>>> cleanup
>>>> and before thread finish.
>>>>
>>>> Kind regards, Thomas
>>>>
>>>>
>>>
>


More information about the hotspot-runtime-dev mailing list