Community
Participate
Working Groups
Having the ability to issue command line debugging commands is important for accessing advanced capabilities not present in the UI. It is also a feature that power debugger users want to have. There is limited command input support today, but it is inadequate.
Alain is working on the gdb console support.
Will this support be generic so that other debuggers that plug in will be able to utilize the console?
PR was not targeted to any particular release. Changing target milestone to 2.1
> Will this support be generic so that other debuggers that plug in will be able > to utilize the console? Yes. For now it is a decision up to the backend to "add" to the debug launch a "fake" Process that will allow it to accept command inputs. Did you want something more abstract like a general Command console facility ?
>For now it is a decision up to the backend to "add" to the debug launch >a "fake" Process that will allow it to accept command inputs. I will take a look at this and see if it serves. >Did you want something more abstract like a general Command console facility ? In general, that is what I was thinking. The more work the general class(es) do, the less the consumer of that class will have to do (or those that derive from it for more specialized purposes). But as I said, over the next month I will be plugging our debugger into Eclipse, so I will see whether the current implementation will serve the purpose.
> In general, that is what I was thinking. The more work the general class (es) > do, the less the consumer of that class will have to do (or those that derive > from it for more specialized purposes). Yes, but we do not forsee to do this before CDT-3.0
Future means you commit to fix it in the Future. Inboxes can't make committments. Moving to '--'.
