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

nsk test fails to compare NotifyFramePop() calls with JVMDI_EVENT_FRAME_POPs

    XMLWordPrintable

    Details

    • Subcomponent:
    • Resolved In Build:
      hopper
    • CPU:
      generic, x86, sparc
    • OS:
      generic, linux, solaris_8
    • Verification:
      Verified

      Description



      Name: abR10010 Date: 11/12/2001


      Test : nsk/regression/b4340444
      TestBase : testbase_nsk

      The nsk/regression/b4340444 test fails to get matching between NotifyFramePop()
      function calls and JVMDI_EVENT_FRAME_POP events under the HotSpot VM
      (build 1.4.0-rc-b85).

      This test calls the NotifyFramePop() function for every methods of the b4340444a
      class and then expects that the JVMDI_EVENT_FRAME_POP event should be generated.

      But the test shows that some JVMDI_EVENT_FRAME_POP events are lost and this
      failure is shown starting with HotSpotVM (build 1.4.0-beta3-b81).

      This failure happens on all platforms.


      To reproduce the bug run in GammaBase/Bugs/<this bug number> directory:

          sh doit.sh <JAVA_HOME> <JAVA_OPTIONS>
          
      See test log for the Solsparc platform:

      % doit.sh .../java/dest/jdk1.4.0beta-b85/solsparc
      java version "1.4.0-rc"
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-rc-b85)
      Java HotSpot(TM) Client VM (build 1.4.0-rc-b85, mixed mode)
      ==> nsk/regression/b4340444 test LOG:
      --> This test on #4340444 bug; Category: hotspot; Subcategory: jvmdi
          Synopsis: Number of frame pops doesn't seem to match number of method entry
      events

      --> b4340444: execution of b4340444a class methods ...
      --> b4340444: execution of b4340444a class methods completed

      ##> b4340444: Failure: NotifyFramePop() calls number does NOT match
      JVMDI_EVENT_FRAME_POP number
      --> total NotifyFramePop() calls = 408
      --> total JVMDI_EVENT_FRAME_POP = 378
      --> Number of b4340444a.methods for which NotifyFramePop() was called = 12
      --> Number of b4340444a.methods for which JVMDI_EVENT_FRAME_POP was caught = 6

      --> List of methods for which NotifyFramePop calls does NOT match to
      JVMDI_EVENT_FRAME_POP:
      ---> method name = <clinit>; class source file name = b4340444a.java
           NotifyFramePop calls = 1; JVMDI_EVENT_FRAME_POP number = 0 (UNEXPECTED
      result)
      ---> method name = <init>; class source file name = b4340444a.java
           NotifyFramePop calls = 1; JVMDI_EVENT_FRAME_POP number = 0 (UNEXPECTED
      result)
      ---> method name = exceptionN1; class source file name = b4340444a.java
           NotifyFramePop calls = 1; JVMDI_EVENT_FRAME_POP number = 0 (UNEXPECTED
      result)
      ---> method name = exceptionN2; class source file name = b4340444a.java
           NotifyFramePop calls = 1; JVMDI_EVENT_FRAME_POP number = 0 (UNEXPECTED
      result)
      ---> method name = exceptionN3; class source file name = b4340444a.java
           NotifyFramePop calls = 1; JVMDI_EVENT_FRAME_POP number = 0 (EXPECTED
      result)
      ---> method name = exceptionN4; class source file name = b4340444a.java
           NotifyFramePop calls = 1; JVMDI_EVENT_FRAME_POP number = 0 (EXPECTED
      result)
      ---> method name = class_test_method_without_param; class source file name =
      b4340444a.java
           NotifyFramePop calls = 100; JVMDI_EVENT_FRAME_POP number = 94 (UNEXPECTED
      result)
      ---> method name = class_test_method_with_param; class source file name =
      b4340444a.java
           NotifyFramePop calls = 100; JVMDI_EVENT_FRAME_POP number = 94 (UNEXPECTED
      result)
      ---> method name = object_test_method_without_param; class source file name =
      b4340444a.java
           NotifyFramePop calls = 100; JVMDI_EVENT_FRAME_POP number = 94 (UNEXPECTED
      result)
      ---> method name = object_test_method_with_param; class source file name =
      b4340444a.java
           NotifyFramePop calls = 100; JVMDI_EVENT_FRAME_POP number = 94 (UNEXPECTED
      result)

      ==> nsk/regression/b4340444 test FAILED
      Exit Code: 97


      The 64-bit Server VM loses the JVMDI_EVENT_FRAME_POP event only
      for method which catches Exception:

      % doit.sh .../java/dest/jdk1.4.0beta-b85/solsparc -d64
      java version "1.4.0-rc"
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-rc-b85)
      Java HotSpot(TM) 64-Bit Server VM (build 1.4.0-rc-b85, interpreted mode)
      ==> nsk/regression/b4340444 test LOG:
      --> This test on #4340444 bug; Category: hotspot; Subcategory: jvmdi
          Synopsis: Number of frame pops doesn't seem to match number of method entry
      events

      --> b4340444: execution of b4340444a class methods ...
      --> b4340444: execution of b4340444a class methods completed

      ##> b4340444: Failure: NotifyFramePop() calls number does NOT match
      JVMDI_EVENT_FRAME_POP number
      --> total NotifyFramePop() calls = 408
      --> total JVMDI_EVENT_FRAME_POP = 405
      --> Number of b4340444a.methods for which NotifyFramePop() was called = 12
      --> Number of b4340444a.methods for which JVMDI_EVENT_FRAME_POP was caught = 9

      --> List of methods for which NotifyFramePop calls does NOT match to
      JVMDI_EVENT_FRAME_POP:
      ---> method name = exceptionN2; class source file name = b4340444a.java
           NotifyFramePop calls = 1; JVMDI_EVENT_FRAME_POP number = 0 (UNEXPECTED
      result)
      ---> method name = exceptionN3; class source file name = b4340444a.java
           NotifyFramePop calls = 1; JVMDI_EVENT_FRAME_POP number = 0 (EXPECTED
      result)
      ---> method name = exceptionN4; class source file name = b4340444a.java
           NotifyFramePop calls = 1; JVMDI_EVENT_FRAME_POP number = 0 (EXPECTED
      result)

      ==> nsk/regression/b4340444 test FAILED
      Exit Code: 97

      Please note that the attached in Gammabase nsk/regression/b4340444 test
      is not the same as in the promoted testbase_nsk.v14r08.

      This test was fixed according to #4445833 bugreport and it'll be promoted
      with the testbase_nsk.v14r10 release.


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

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              tbell Tim Bell
              Reporter:
              bondsunw Bond Bond (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: