RFR: 8210235: JvmtiTrace::safe_get_current_thread_name is unsafe in debug builds
kim.barrett at oracle.com
Fri Aug 31 18:05:49 UTC 2018
> On Aug 31, 2018, at 2:01 PM, coleen.phillimore at oracle.com wrote:
> Looks good and trivial.
> On 8/30/18 3:24 PM, Kim Barrett wrote:
>> Please review this trivial change to avoid a possible assert, by
>> calling Thread::current_or_null rather than Thread::current in a
>> context where the NULL case is explicitly handled.
>> Locally (linux-64) verified change builds and ran some tests for
>> smoke. I couldn't find any tests involving TraceJVMTI.
More information about the hotspot-runtime-dev