Community
Participate
Working Groups
The method CApplicationLaunchShortcut#findLaunchConfiguration() assumes we are using the CDI debugger. In doing that, it tries to select the debugger type to use, and may prompt the user if it cannot choose a single one. Neither DSF-GDB nor EDC use those debugger types, and therefore, such a prompt would be quite confusing for the user. I suggest we simply check which launch delegate will be used and if it is not the CDI one, ignore that piece of code. I'll write a patch.
Why not just check which debugger is associated with the toolchain in the current build config and use that one instead of prompting. Oh, wait :P
(In reply to comment #1) > Why not just check which debugger is associated with the toolchain in the > current build config and use that one instead of prompting. Oh, wait :P Is this guaranteed to work? When I test, I never actually get the prompt because of this toolchain check. But the code does prepare for the possibility that this check will not yield a debugger (or a single one). That is the part that had me worried. What do you think, do we need a check for DSF-GDB and EDC, or is the toolchain check enough?
