Bug ID: JDK-6780119 hs104t002 fires assert(0 <= i && i

Type: Bug
Component: hotspot
Sub-Component: jvmti
Affected Version: 7

Priority: P4
Status: Closed
Resolution: Cannot Reproduce
OS: generic
CPU: generic

Submitted: 2008-12-03
Updated: 2023-12-13
Resolved: 2016-12-07

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
tbdResolved

An entry from my nightly analysis report:

New nsk.jvmti failures (from 2008.11.26)
*   nsk/jvmti/scenarios/hotswap/HS104/hs104t002
        This test failed the following assertion on Win-AMD64 Server VM
        (machine vm-x2200-02):

            Internal Error (src/share/vm/oops/cpCacheOop.hpp:317)
            Error: assert(0 <= i && i < length(),"index out of bounds")

        The hs_err_pid file shows that the crash happened in
        CompilerThread0. The current CompileTask is:

            C2: 44   b  nsk.jvmti.scenarios.hotswap.HS104.hs104t002.MyThread.doIt()V (25 bytes)

        The MyThread class is the target of JVM/TI RedefineClass() for
        this test.

The nightly URL:
http://sqeweb.sfbay.sun.com/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2008-11-26/Serv_Baseline/vm/windows-amd64/server/comp/windows-amd64_server_comp_nsk.jvmti.testlist/analysis.html

Relates :	JDK-6773838 - There is no calling stack for Compiler thread in hs_err file on x86
Relates :	JDK-5088035 - hotswap fires assert(0 <= i && i < length(),"index out of bounds")