getThreadName() should not crash

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.0.12, 6.0.2, 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v6.0, v5.0
    • Service Arch 2022-05-16, Service Arch 2022-05-30
    • 2
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If getThreadName() is invoked before ThreadContextsInitialized is complete, a SIGSEGV will happen. The name is typically needed for debugging and logging purposes and should not cause a crash. This ticket is to implement a mitigation to SIGSEGV

              Assignee:
              Billy Donahue
              Reporter:
              Sergey Galtsev (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: