United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-5098422 NPE with no stack Trace: Enable -XX:-OmitStackTraceInFastThrow for 1.4.2
JDK-5098422 : NPE with no stack Trace: Enable -XX:-OmitStackTraceInFastThrow for 1.4.2

Details
Type:
Bug
Submit Date:
2004-09-08
Status:
Resolved
Updated Date:
2004-10-13
Project Name:
JDK
Resolved Date:
2004-09-20
Component:
hotspot
OS:
solaris_7
Sub-Component:
compiler
CPU:
sparc
Priority:
P2
Resolution:
Fixed
Affected Versions:
1.4.2_07
Fixed Versions:
1.4.2_07 (b01)

Related Reports
Relates:

Sub Tasks

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.

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

                                    

Comments
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
                                     
2004-09-08
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
                                     
2004-09-08
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
                                     
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


                                     
2004-10-02



Hardware and Software, Engineered to Work Together