Community
Participate
Working Groups
The "Terminate All" action works by recursively going through all the launches and debug targets in the debugger and calling canTerminate() then terminate(). If canTerminate() returns false, debugger calls canDisconnect() followed by disconnect(). So the action doesn't perform as advertized and should renamed. We have a debugger in which the debug target cannot be terminated, but the threads under the target can be. When "Terminate All" is called, some users expect that all of their threads will be terminated, while others expect that the debug target will be disconnected. Hopefully just renaming the action to say what it actually does will solve the problem, but alternatively the action could be split into two "Terminate All" and "Disconnect All" which would do what they say.
Deferred for post 3.1 consideration.
Reopening to consider sometime in 3.4. Action can be renamed to "Terminate/Disconnect All". Help topic for this item should be updated as well (since it currently says nothing about it disconnecting if terminate fails. Other terminate actions, such as terminate and remove, should be checked to see if they attempt a disconnect.
Fixed in HEAD. Updated ActionMessages.properties. Updated help (both context file and html).
Mike, please verify.
updated links for commands that link to the Terminate All/Disconnect All verified