-
Bug
-
Resolution: Fixed
-
P3
-
hs23
-
b01
-
generic
-
os_x
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2221733 | 8 | Staffan Larsen | P3 | Closed | Fixed | b28 |
JDK-8018121 | 7u45 | Staffan Larsen | P3 | Closed | Fixed | b01 |
JDK-8002397 | 7u40 | Staffan Larsen | P3 | Closed | Fixed | b01 |
JDK-2224524 | 7u6 | Staffan Larsen | P3 | Closed | Fixed | b10 |
JDK-2221373 | hs23.2 | Staffan Larsen | P3 | Closed | Fixed | b01 |
is a 8-byte value rather a 4-byte value as it is on the other supported platforms.
Java Flight Recorder currently relies on the thread id being 4 rather than 8 bytes,
and it would require a file format change to switch. The thread id is an identifier
and doesn't appear to be used for anything else on OSX.
Rather than change file formats, it might be possible to instead use a mach_port_t,
which is an unsigned int (and thus 4 bytes). To get it, use
mach_port_t tid = pthread_mach_thread_np(pthread_self());
- backported by
-
JDK-2221373 Use a mach_port_t as the OSThread thread_id rather than pthread_t on BSD/OSX
- Closed
-
JDK-2221733 Use a mach_port_t as the OSThread thread_id rather than pthread_t on BSD/OSX
- Closed
-
JDK-2224524 Use a mach_port_t as the OSThread thread_id rather than pthread_t on BSD/OSX
- Closed
-
JDK-8002397 Use a mach_port_t as the OSThread thread_id rather than pthread_t on BSD/OSX
- Closed
-
JDK-8018121 Use a mach_port_t as the OSThread thread_id rather than pthread_t on BSD/OSX
- Closed
- relates to
-
JDK-8022737 Build failed on FreeBSD because thread_id_t is not u4
- Closed