Bug ID: JDK-6231558 JVM outputs exceptions or crash with a program using Big interger in 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_08 b03Fixed

A customer has found out an exception(or crash) in 1.4.2_08b02.

REPRODUCE :
  (1) Compile the attached program, Big.java
  (2) Launch "java -client Big 5" in 1.4.2_08b02
  (3) The following message will appears.

K:\tmp>java -version
java version "1.4.2_08"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b02)
Java HotSpot(TM) Client VM (build 1.4.2_08-b02, mixed mode)

K:\tmp>javac *.java

K:\tmp>java -client Big 5
java.lang.NullPointerException
        at java.math.BigInteger.toString(BigInteger.java:2583)
        at java.math.BigInteger.toString(BigInteger.java:2613)
        at Big.run(Big.java:17)
java.lang.NullPointerException
        at java.math.BigInteger.toString(BigInteger.java:2583)
        at java.math.BigInteger.toString(BigInteger.java:2613)
        at Big.run(Big.java:17)
java.lang.NumberFormatException: For input string: "null"
        at java.lang.NumberFormatException.forInputString(NumberFormatException.
java:48)
        at java.lang.Integer.parseInt(Integer.java:468)
        at java.math.BigInteger.<init>(BigInteger.java:314)
        at java.math.BigInteger.<init>(BigInteger.java:447)
        at Big.run(Big.java:16)

CONFIGURATION :
  JRE/JDK : 1.4.2_08b02
  OS      : WindowsXP(SP1, Japanese)

NOTE:
  This seems related to 6215242 and might be regression.

###@###.### 2005-2-22 09:10:49 GMT

EVALUATION This bug has the same root cause as 4917709. A bailout was removed in 1.4.1 which led to 4917709, which was an attempt to compile the previously-failing methods properly. Unfortunately due to constraints in the 1.4.x C1 code generator it's basically impossible for the compiler to generate correct debug and oop map information for these situations. The fix is to reintroduce the bailout that was present in 1.4.0. This bug is also related to 6215242 though the fix for that bug didn't introduce this one; the customer's test case fails with an unmodified 1.4.2 JVM. The bailout will be reintroduced under this bug ID and 6232217 (which is actually a regression of 4917709 caused by the fix for 6215242) will be closed as a duplicate of this one since they both have the same root cause. ###@###.### 2005-2-25 03:05:44 GMT

22-02-2005

Duplicate :	JDK-6232217 - Regression: test for failing for 1.4.2_08 b02 but passes for 1.4.2_08 b01 on Cinnebar
Relates :	JDK-4917709 - SEGV in MapLoops test
Relates :	JDK-6239336 - JVM internal error/EXCEPTION_ACCESS_VIOLATION, possibly memory related?
Relates :	JDK-6215242 - ShouldNotReachHere() failure at hotspot/src/cpu/i486/vm/c1_FrameMap_i486.cpp, 92