Details
P2 Description
When a debugger uses sun.tools.debug, and the program it is
debugging exits, the RemoteDebugger is supposed to make a
callback to quitEvent().
My experience is that sometimes this callback is made,
and more often it isn't made. Often (if the debugger
is run in verbose mode, which can be done by typing "jdb
-dbgtrace" if using jdb) there is a printToConsole event
saying
[debugger: junk.main() exited]
but no corresponding quitEvent() call. I can rerun the
same program and sometimes get quitEvent(), sometimes not.
How can a debugger reliably know when the program being
debugged has exited?
debugging exits, the RemoteDebugger is supposed to make a
callback to quitEvent().
My experience is that sometimes this callback is made,
and more often it isn't made. Often (if the debugger
is run in verbose mode, which can be done by typing "jdb
-dbgtrace" if using jdb) there is a printToConsole event
saying
[debugger: junk.main() exited]
but no corresponding quitEvent() call. I can rerun the
same program and sometimes get quitEvent(), sometimes not.
How can a debugger reliably know when the program being
debugged has exited?
Attachments
Issue Links
- duplicates
-
JDK-4039813 DebuggerCallback.quitEvent() not received after RemoteThread.cont()
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-