This is only a problem for a debug build of the 1.4 or 1.4.1 VM and is
just an ease-of-debugging issue.

If you are running with -Xint and expecting -XX:+VMStackTraceAtException
to show all exceptions thrown by the program, then exceptions that are
created by the interpreter via InterpreterRuntime::create_exception will
not show up in the printouts.

This problem exists in 1.4.0.01 and 1.4.1b17 sources. It would probably
help someone debugging the early stage of a port if VMStackTraceAtException
showed all the exceptions.

To fix this, in InterpreterRuntime::create_exception add a call to
Exceptions::debug_trace after the call to Exceptions::new_exception.
There may be some other calls to Exceptions::new_exception which are
also missed by VMStackTraceAtException.