See bug id: 4292742

That bug is fixed in 1.4.2_05, with the ficed code-path being invocable through the use of -XX:+FullSpeedJVMDI.

However in tiger, as well in the 1.3.1 code-base, the same effect is fetched from the JVM through the use of the jvm-option: -XX:+OmitStackTraceInFastThrow.

1.4.2 needs to be corrected so as to be able to deliver befaviour the same as in tiger, as well as 1.3.1, when invoked with the same option as in the other two: -XX:+OmitStackTraceInFastThrow.

###@###.### 2004-09-08