JDK-4917709 : SEGV in MapLoops test
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 1.4.2,1.4.2_03,5.0
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: linux_redhat_7.2,solaris_8,windows_xp
  • CPU: x86
  • Submitted: 2003-09-05
  • Updated: 2004-08-17
  • Resolved: 2003-09-30
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 Availabitlity Release.

To download the current JDK release, click here.
1.4.2_06 06Fixed
Related Reports
Duplicate :  
Duplicate :  
Relates :  
Relates :  
Relates :  
Relates :  
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.

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

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