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.