JVMDI test b4340444 fails in 64-bit server VM in all the modes.

To reproduce go to /net/jano.sfbay/export/disk20/GammaBase/Bugs/b4340444
run the doit.ksh as ksh doit.ksh.

Failure
==> 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: because of Exception)
---> method name = exceptionN4; class source file name = b4340444a.java
     NotifyFramePop calls = 1; JVMDI_EVENT_FRAME_POP number = 0 (EXPECTED result: because of Exception)

==> nsk/regression/b4340444 test FAILED


The failure is easily reproducible in machine yetoom.