Community
Participate
Working Groups
On Linux, when a user steps out of a main method, the VM throws a disconnected exception. This does not happen on other platforms. The result is that an error dialog appears describing the "VMDisconnect" exception, but there are no bad side effects (the debug target then appears as terminated, as expected). Unsure of good fix, as this is a special case of "if stepping out of main, and on Linux, ignore disconnect exception". Problem occurred on IBM 1.3.0 VM cx130-20010502.
Problem does not occurr on JDK1.4
Does the VM really disconnect when you step out of main, or does it disconnect when there are no more running threads? It actually doesn't seem unreasonable to disconnect in the latter case. Easiest fix: Add a "Print stack trace on VM disconnect" option and clear it by default.
*** This bug has been marked as a duplicate of 7804 ***