| Re: [cdt-dev] Access to Full Gdb Console input |
No, I had not thought about allowing to extend the new console by intercepting the input. I think it is a good idea.
Currently the class GdbTerminalConnector.java simply passes the I/O from gdb (non-mi) directly to the view (terminal widget) and vice versa.
We could add a listener facility that could be registered with, to get all input and all output of that console.
The complexity will probably be to parse that information so it can be mapped to actual gdb command. This could be done by the listener though. The important part is to provide the hook to get the info.
Are you willing to give it a try? It would be reviewed quickly since all this code is fresh in our minds :)
We could even go further and allow to modify the I/O before it goes to gdb or is shown to the user, but this is more complicated to do.
About the breakpoint: did you mean that a breakpoint is created in eclipse when you create one in the gdb console? If so, then yes, that is by design where our BreakpointSynchronizer makes sure eclipse knows about such console-created breakpoints so it can show them in the editor.
Feel free to ask for any clarification
Marc