JDK-4336145 : hotspot exits on unexpected signals
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.3.0
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_8
  • CPU: generic
  • Submitted: 2000-05-05
  • Updated: 2006-02-02
  • Resolved: 2006-02-02
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.
Other
1.3.0 sol-beta2Fixed
Related Reports
Relates :  
JDK-6694099 - Hotspot vm_exit_out_of_memory should dump core
Description
If an unexpected signal is received (especially from outside the VM),
hotspot exits, neither producing a core file nor providing an 
event which can be caught in a debugger.

For developers of native methods, this means that there is no way
to stop in the debugger at the time of the signal to examine the 
state of the native method.

For customer service (both ours and third party software providers)
the lack of core file means that there is no remaining evidence of 
the failure.  This will be a particular problem for intermittent failures
at customer sites.

Since the debug (_g) versions of JDK components are not shipped to
customers as part of the production release, we cannot have the customer
run java_g.  Neither is classic or any other VM included in the release.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: kest-sol-beta2 FIXED IN: kest-sol-beta2 INTEGRATED IN: kest-sol-beta2
14-06-2004
EVALUATION john.coomes@eng 2000-05-08 Suggested fix would solve the problem; workaround is to use the flag -XX:+ShowMessageBoxOnError. The policy has been not to dump core with product builds. Not sure why; will try to find out.
11-06-2004
WORK AROUND john.coomes@eng 2000-05-08 The (undocumented) flag -XX:+ShowMessageBoxOnError will cause the vm to print the message 'Do you want to debug the problem?' and wait for input instead of exiting. [Similar to the 1.2 production JDK behavior with _JVM_ARGS=panic_suspend.] Can attach the debugger or run gcore manually at that point.
11-06-2004
SUGGESTED FIX Remove the #ifndef PRODUCT from os::abort(). john.coomes@eng 2000-05-31 As suggested in comments, add a boolean argument to os::abort() that determines whether a core file is generated (default to true); pass false when calling from jni_FatalError to avoid a JCK test failure.
11-06-2004