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
|