-
Type:
Enhancement
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 7u45, 8
-
Component/s: hotspot
-
b64
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8082665 | emb-9 | Max Ockner | P3 | Resolved | Fixed | team |
| JDK-8149226 | 8u101 | David Buck | P3 | Resolved | Fixed | b01 |
| JDK-8144713 | 8u92 | David Buck | P3 | Resolved | Fixed | b01 |
| JDK-8155322 | emb-8u101 | David Buck | P3 | Resolved | Fixed | b01 |
| JDK-8144772 | 7u101 | David Buck | P3 | Resolved | Fixed | b01 |
Currently on crash we display the signal and thread info as:
SIGSEGV (0xb) at pc=0x00007fc2e3689320, pid=11605, tid=140475482081024
It would be much more useful if the thread id was displayed as hex - the decimal version could be displayed next to it inside a braces (if useful), or the other way around.
SIGSEGV (0xb) at pc=0x00007fc2e3689320, pid=11605, tid=140475482081024
It would be much more useful if the thread id was displayed as hex - the decimal version could be displayed next to it inside a braces (if useful), or the other way around.
- backported by
-
JDK-8082665 Thread id should be displayed as hex number in error report
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-