Bug ID: JDK-5098422 NPE with no stack Trace: Enable -XX:-OmitStackTraceInFastThrow for 1.4.2

Versions (Unresolved/Resolved/Fixed)

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.4.2_07 b01Fixed

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

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.4.2_07 FIXED IN: 1.4.2_07 INTEGRATED IN: 1.4.2_07
02-10-2004
SUGGESTED FIX mage:"/net/mage.india/space/1.4.2/hotspot/src/share/vm/runtime" 287 $ diff globals.hpp /net/nightsvr/exp3/1.4.2/hotspot/src/share/vm/runtime/globals.hpp 1224,1226d1223 < product(bool, OmitStackTraceInFastThrow, true, < "Omit backtraces for some 'hot' exceptions in optimized code") < \ mage:"/net/mage.india/space/1.4.2/hotspot/src/share/vm/opto" 292 $ diff parse3.cpp /net/nightsvr/exp3/1.4.2/hotspot//src/share/vm/opto/parse3.cpp 442c442 < if (FullSpeedJVMDI \|\| !OmitStackTraceInFastThrow) { --- > if (FullSpeedJVMDI) { 444,445c444 < // Do not optimize away backtraces if -XX:+FullSpeedJVMDI or < // -XX:-OmitStackTraceInFastThrow is given. --- > // Do not optimize away backtraces if -XX:+FullSpeedJVMDI is given. This bug, and its fix is to avoid the possibility of a customer seeing the perception of a regression in the flags-usage when invoking the JVM, while upgrading from 1.3.1 to 1.4.2. ###@###.### 2004-09-08
08-09-2004
PUBLIC COMMENTS This bug, and its fix is to avoid the possibility of a customer seeing the perception of a regression in the flags-usage when invoking the JVM, while upgrading from 1.3.1 to 1.4.2. ###@###.### 2004-09-08
08-09-2004
EVALUATION This bug, and its fix is to avoid the possibility of a customer seeing the perception of a regression in the flags-usage when invoking the JVM, while upgrading from 1.3.1 to 1.4.2. ###@###.### 2004-09-08
08-09-2004