Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4345361

RequestEvent: Fatal: must own lock Threads_lock

XMLWordPrintable

    • beta
    • generic
    • generic
    • Not verified



        Name: dkR10031 Date: 06/13/2000


        Both Kestrel win32 FCS and Kestrel Solaris beta HotSpot VMs fail the
        test nsk/jvmpi/events/thrstart003 from testbase_nsk in debug mode.
        Invocation of RequestEvent crashes VM with Internal Error.

        This happens only in debug mode, otherwise the test passes.

        To reproduce the bug run
        doit.sh <jdk root directory>
        in
        /net/sqesvr/vsn/GammaBase/Bugs/<this bug number>

        The test produces the output:

        $ doit.sh /export/ld24/java/hotspot/Solaris_JDK_1.3
        java version "1.3.0"
        Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-beta)
        Java HotSpot(TM) Client VM (build 1.3-beta-debug, mixed mode)
        THREAD_START: Thread-0 main system 4093839104 3408848
        check 0: lastThrID = 4093839104
        #
        # HotSpot Virtual Machine Error, Internal Error
        # Please report this error at
        # http://java.sun.com/cgi-bin/bugreport.cgi
        #
        # Fatal: must own lock Threads_lock
        #
        # Error ID:
        /export/sail1/jdk1.3_b17/hotsparc-1.3-b17/src/share/vm/runtime/mutexLocker.cpp,
        86
        [ Patched ]
        #
        # Problematic Thread: prio=5 tid=0x3e010 nid=0x1 runnable
        #
        Dumping core....
        Abort

        ======================================================================

              acorn Karen Kinnear (Inactive)
              dimasunw Dima Dima (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: