Community
Participate
Working Groups
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729) Build Identifier: I20090611-1540 When the various launch actions create an Expression to evaluate for purposes of enabling a particular shortcut, that evaluation may throw an exception. That exception is not being handled in a meaningful way, which makes troubleshooting broken shortcuts challenging. Consider these two locations where the catch block is empty. LaunchShortcutsAction:168 ContextualLaunchAction:221 Perhaps in these cases the status could at least be logged? Reproducible: Always Steps to Reproduce: 1. Set up a launch shortcut extension with an enablement clause. 2. Use the typical (with selection) -> (iterate) -> (some property tester that won't accept the type) 3. Fill a launch shortcut menu which causes the evaluation to fall out early due to broken property tester.
Created attachment 149173 [details] Proposed patch against HEAD
Created attachment 149257 [details] Revised patch I noticed LaunchConfigurationManager has some handling that appears to make sense in the places I already mentioned; patch revised accordingly.
Reasonable request.
Pushed the fix to master. http://git.eclipse.org/c/platform/eclipse.platform.debug.git/commit/?id=757835f722211c4acd2d534fe565d7fba0e640a7