Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8210235

JvmtiTrace::safe_get_current_thread_name is unsafe in debug builds

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Fixed
    • Icon: P4 P4
    • 12
    • None
    • hotspot
    • None
    • b10
    • generic
    • generic

      The no-arg overload of JvmtiTrace::safe_get_current_thread_name calls the one-arg overload with the result of Thread::current(). In a debug build this will assert if there is no current Thread. It should instead pass the result of Thread::current_or_null(), and let the existing NULL check in the one-arg function handle that case.

            kbarrett Kim Barrett
            kbarrett Kim Barrett
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: