Because of an old test bug, this test have not been run for a long time. After test fix, we sometimes get this assert. This may be another test bug, but since it is a hotspot assert, it may be a product issue.

This does not happen every time. So far I have seen it only on windows and solaris.

aurora run:
http://vmsqe-app.russia.sun.com/surl/b1

Summary from hs_err file:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (C:\jprt\T\P1\000658.sspitsyn\s\hotspot\src\share\vm\prims\jvmtiThreadState.cpp:284), pid=965740, tid=842148
# assert(_cur_stack_depth == count_frames()) failed: cur_stack_depth out of sync
#

RULE nsk/jdi/StepRequest/addClassFilter_rt/filter_rt001 Crash Internal Error ...jvmtiThreadState.cpp...assert(_cur_stack_depth == count_frames()) failed: cur_stack_depth out of sync
RULE nsk/jdi/StepRequest/addClassFilter_rt/filter_rt003 Crash Internal Error ...jvmtiThreadState.cpp...assert(_cur_stack_depth == count_frames()) failed: cur_stack_depth out of sync