P4 | Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2176884 | 7 | Coleen Phillimore | P3 | Closed | Fixed | b12 |
| JDK-2171803 | 6u4 | Coleen Phillimore | P3 | Closed | Fixed | b03 |
When native code crashes in third party libraries, give a big message that the crash isn't in the hotspot VM/JDK in the hs_err_pid*.log file. Eg, from bug 6444811 which is a libGL bug:
# An unexpected error has been detected by Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xe79f5ea8, pid=4393, tid=3
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0-rc-b87 mixed mode)
# Problematic frame:
# C [libGL.so.1+0x2bea8]
#
# THE ERROR IS CAUSED BY NATIVE CODE OUTSIDE THE JAVA RUNTIME ENVIRONMENT.
#
Except when the library is libc.so because that could be caused by the VM. Not sure if there are other libraries to exclude for this message.
# An unexpected error has been detected by Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xe79f5ea8, pid=4393, tid=3
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0-rc-b87 mixed mode)
# Problematic frame:
# C [libGL.so.1+0x2bea8]
#
# THE ERROR IS CAUSED BY NATIVE CODE OUTSIDE THE JAVA RUNTIME ENVIRONMENT.
#
Except when the library is libc.so because that could be caused by the VM. Not sure if there are other libraries to exclude for this message.
- backported by
-
JDK-2171803 Make hs_err_pid*file say CRASHED IN NATIVE CODE OUTSIDE THE JDK if crash outside VM.
-
- Closed
-
-
-
- Closed
-