Due to the fix (which we badly needed) for 4336145, hotspot now dumps
core for any vm_exit_during_initialization even in product mode.
The problem was seen on Kestrel Solaris beta almost b17.
There are times when a core dump is not needed, and inappropriate.
The example found was in mistyping a library name, as in
java -Xrunlibreqevent008 reqevent008 instead of typing
java -Xrunreqevent008 reqevent008
What I got back was:
Error occurred during initialization of VM
Could not find -Xrun library: liblibreqevent008.so
Abort (core dumped)
The request is to split errors into those where a core dump is helpful
and those where it is overkill.
core for any vm_exit_during_initialization even in product mode.
The problem was seen on Kestrel Solaris beta almost b17.
There are times when a core dump is not needed, and inappropriate.
The example found was in mistyping a library name, as in
java -Xrunlibreqevent008 reqevent008 instead of typing
java -Xrunreqevent008 reqevent008
What I got back was:
Error occurred during initialization of VM
Could not find -Xrun library: liblibreqevent008.so
Abort (core dumped)
The request is to split errors into those where a core dump is helpful
and those where it is overkill.
- relates to
-
JDK-4651918 Core dump with non existing runlibrary
- Closed
-
JDK-6644629 JVM dies with little/misleading problem information during excessive creation of ORB threads
- Closed
-
JDK-4418494 test nsk/regression/b4343963 crashes java_g VM
- Closed
-
JDK-6694099 Hotspot vm_exit_out_of_memory should dump core
- Closed
-
JDK-4651882 Core dump with bogus bootclasspath
- Closed