Name: chT40241 Date: 10/22/97


The Problem
Start any java_g command line in a console window. Then type ctrl-break:

A loop results printing the heading "Full thread dump:". It is very
difficult to remove the looping program from the system. This problem
seems to be the same problem as 4083547, excpet that it occurs at 1.1.5
rather than 1.2.

Text from that problem describing the cause is as follows:

The VM is immediately terminated, due to an assertion failure on line 537 of threads_md.c. Comments in DumpThreads in debug.c indicate that under Windows, it is impossible to lock the thread queue during a ctrl-break, which means that threads_md.c ought not to abort if the queue is not locked. This is a serious impediment to debugging when using the java_g version of Java.

The 1.2 version of Java terminates rather than looping due to this error. The difference seems to be that the panic routine of 1.1.5 itself calls DumpThreads, which is a really bad idea when DumpThreads is in the calling chain for panic.

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