JDK-6447373 : Make hs_err_pid*file say CRASHED IN NATIVE CODE OUTSIDE THE JDK if crash outside VM.
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 6
- Priority: P4
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2006-07-10
- Updated: 2012-10-13
- Resolved: 2007-04-24
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 6 | JDK 7 | Other |
|---|---|---|
6u4Fixed  |
7Fixed |
hs10Fixed |
Description
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.
Comments
|