United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-4917709 : SEGV in MapLoops test

Details
Type:
Bug
Submit Date:
2003-09-05
Status:
Resolved
Updated Date:
2004-08-17
Project Name:
JDK
Resolved Date:
2003-09-30
Component:
hotspot
OS:
solaris_8,linux_redhat_7.2,windows_xp
Sub-Component:
compiler
CPU:
x86
Priority:
P2
Resolution:
Fixed
Affected Versions:
1.4.2,1.4.2_03,5.0
Fixed Versions:
1.4.2_06 (06)

Related Reports
Backport:
Duplicate:
Duplicate:
Relates:
Relates:
Relates:
Relates:

Sub Tasks

Description
The attached test program causes the VM to abort with a SEGV around 30%
of the time on Intel systems with the -client option.

The source fine must be compiled with the "-source 1.5" option.  It requires
a J2SE build with the JSR-166 library changes which can be found under:

  /home/mb29450/ws/jsr166/build/solaris-i586  (solaris-x86)
  /net/polgar/u/martin/src/jsr166/images      (other systems)

The failure usually occurs in java.util.concurrent.ConcurrentHashMap$Segment.get(), but  I don't see anything
obviously wrong with the generated code for this method.  It may just be
using a value that was corrupted someplace else.

                                    

Comments
CONVERTED DATA

BugTraq+ Release Management Values

COMMIT TO FIX:
1.4.2_06
generic
tiger

FIXED IN:
1.4.2_06
tiger

INTEGRATED IN:
1.4.2_06
tiger
tiger-b22


                                     
2004-09-11
EVALUATION

This is a old bug that we're just finding.  It was introduced some time in 1.4.1.  There used to be a bailout if the stack wasn't empty at backward branches because the oopmap ends up skipping any values which are in spills on the expression stack.  This bug shouldn't hold up the integration of the JSR166 changes.
###@###.### 2003-09-18
                                     
2003-09-18



Hardware and Software, Engineered to Work Together