JDK-6549844 : Wording problems in "An unexpected error has been detected by Java Runtime Environment"
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2007-04-24
  • Updated: 2011-04-20
  • Resolved: 2011-04-20
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.
JDK 6 Other
6u14Fixed hs12Fixed
Description
The above message appears at the start of an hs_err file.
It implies that some errors are expected.
Also, it seems to me that 'the' should precede 'Java ...'.

The message should be changed to something like
   A fatal error has been detected by the Java Runtime Environment
The VM also will report that a problem has happened outside the VM for crashes within compiler threads, which is not true.

#
#  Internal Error (/net/philli/scratch1/coleenp/ws/compall.ws/src/share/vm/opto/matcher.cpp:1363), pid=19258, tid=9
#  Error: assert(false,"bad AD file")
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (11.0-b08-compall.ws_0126_1659-fastdebug mixed mode solaris-sparc)
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
Comments
EVALUATION Fixed 6549844: Wording problems in "An unexpected error has been detected by Java Runtime Environment" Changed wording to "A fatal error has been detected by the Java Runtime Environment" which is better English and more descriptive of the fact that the VM has aborted. Also, there was a message added for crashes in native code that didn't take into account that the compiler thread crashes looked like native code because the compiler thread is a Java thread. This is tested extensively in the compressed oops workspace. Webrev: http://jruntime.east/~coleenp/webrev/6549844 Reviewed by: jjh, sbohne, jrose, never (made up fixedin build number).
29-02-2008
EVALUATION Fixing both in vmError.cpp. Tested in compressed oops workspace.
11-02-2008