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

src/share/vm/prims/jvmtiEnv.cpp:457 assert(phase == JVMTI_PHASE_LIVE,"sanity check")

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P4 P4
    • hs16.1
    • 7
    • hotspot
    • b01
    • generic
    • generic

        Here are a couple of assertion failures from my nightly
        analysis report:

        New nsk.jvmti failures (from 2007.10.06)
            nsk/jvmti/AttachOnDemand/attach034
                This test failed the following assertion:

                    Internal Error (src/share/vm/prims/jvmtiEnv.cpp:457)
                    Error: assert(phase == JVMTI_PHASE_LIVE,"sanity check")

                on Solaris SPARC Client VM (machine jtgb4u2e). See similar
                failure for attach043 below.

        The above failure was with a Dolphin-B21 JDK with a newer
        VM, i.e., Dolphin-B22ish VM.


        New nsk.jvmti failures (from 2007.08.21)
            nsk/jvmti/AttachOnDemand/attach043
                This test failed the following assertion:

                    Internal Error (src/share/vm/prims/jvmtiEnv.cpp:457)
                    Error: assert(phase == JVMTI_PHASE_LIVE,"sanity check")

                on Linux AMD64 Server VM (machine bunt).

                Update: Alan believes we have a product bug here since
                    AddToSystemClassLoaderSearch() should be returning a phase
                    error rather than asserting. He also believes we may have a
                    timing bug in the test.

        The above failure was with a Dolphin-B18 JDK with a newer
        VM, i.e., Dolphin-B19ish VM.

              dcubed Daniel Daugherty
              dcubed Daniel Daugherty
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: