default debugger executables

Aleix Pol aleixpol at
Wed Sep 14 23:06:21 UTC 2016

On Wed, Sep 14, 2016 at 6:44 PM, René J.V. Bertin <rjvbertin at> wrote:
> On Wednesday September 14 2016 17:50:53 Aleix Pol wrote:
>> On Wed, Sep 14, 2016 at 9:35 AM, René J.V. Bertin <rjvbertin at> wrote:
>> IIRC the attach action is provided by the debug plugin itself..
> The action of attaching, indeed, yes. Maybe the widget to pick a process to attach to, too, but what difference does it make which KDevelop component provides the feature?
> BTW, I did notice 2 sets of entries in the Run menu on my Linux system where I have both plugins installed. It wouldn't really make sense if that's really because the gdb and lldb plugins both provide the same features. I'm not sure if and how you'd want to expose a debugger choice each time the user moves to debug an already running process, but presenting 2 identical menu items doesn't seem the way to go.

Being 2 disjoint projects, it's unlikely that both of them offer
exactly the same things. Sooner or later some people will start to
prefer lldb for whatever reason or to be able to choose. I'd say it is
acceptable to have them provided that the debugger executable is
installed. When the amount of debublows up, we can fix it.


More information about the KDevelop-devel mailing list