-
Enhancement
-
Resolution: Unresolved
-
P4
-
None
-
None
The original issue is that attached threads don't get their native names set, which is a deliberate design decision (see comments below by @dholmes). But this is especially annoying for ASAN, which only shows meaningless internal thread designators ("T0", "T1", ..). Therefore, and only for ASAN builds, we should set the native names for threads on the OS level.
This issue deliberately excludes the main thread (the thread calling CreateJavaVM), since that thread name will be subject of a separate RFE (see comments below, andJDK-8314091 - that would be a fix in the Java launcher, not in hotspot)
This issue deliberately excludes the main thread (the thread calling CreateJavaVM), since that thread name will be subject of a separate RFE (see comments below, and
- relates to
-
JDK-8175078 Release Note: os::set_native_thread_name() cleanups
-
- Closed
-
-
JDK-8368124 Show useful thread names in ASAN reports
-
- Resolved
-
-
JDK-7102541 RFE: os::set_native_thread_name() cleanups
-
- Closed
-
-
JDK-8314091 Set native thread name for Java main thread
-
- Closed
-
-
JDK-8368365 ASAN errors should produce hs-err files and core dumps
-
- Open
-
-
JDK-8368124 Show useful thread names in ASAN reports
-
- Resolved
-
- links to
-
Review(master) openjdk/jdk/27535
(1 relates to, 1 links to)