|
Quick Lists
|
|
Bug ID:
|
5098422
|
|
Votes
|
0
|
|
Synopsis
|
NPE with no stack Trace: Enable -XX:-OmitStackTraceInFastThrow for 1.4.2
|
|
Category
|
hotspot:compiler2
|
|
Reported Against
|
1.4.2_07
|
|
Release Fixed
|
1.4.2_07(b01)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
2-High
|
|
Related Bugs
|
4292742
|
|
Submit Date
|
08-SEP-2004
|
|
Description
|
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.
xxxxx@xxxxx 2004-09-08
|
|
Work Around
|
N/A
|
|
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.
xxxxx@xxxxx 2004-09-08
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
