Name: wm7046 Date: 06/03/97


The problem can be demonstrated by stepping through the Microsoft animation
sample using our own GUI-based debugger. This hang is timing-sensitive and only
occurs about 20% of the time from our experience. The problem can be reproduced
by stepping through sample.main(). Typically, it will occur toward the bottom of
the function, either before or after stepping over the last call to
frame.show(). If you are unlucky, the debugger target (and debugger) will hang
after one of the steps when the debugger tries to retrieve variable information.

This is with all our SAS-provided JDK fixes in place. If one doesn't have those
fixes on, then you have to be very lucky to get to the point in execution where
this problem could manfest itself.

>From our diagnosis of the bug, it is certainly possible that this problem could
be reproduced with jdb. It would require the use of the print command after each
step. So far, we have not actually reproduced the problem in this manner.
======================================================================