|Re: [cdt-dev] [DSF] why does AbstractMIControl.startCommandProcessing does use concrete GDBBackend class name?|
The fix for bug 327617 came after API freeze, so I couldn't add the hook I needed to IMIBackend.
That interface has getMIInputStream() and getMIOutputStream() but does not have getMIErrorStream()
The way I found to work around this limitation was to get the gdbProcess from GDBBackend directly,
but that method is not part of an interface either.
I assume that your version of IGDBBackend does not extend GDBBackend and that you are getting
I think overriding startCommandProcessing() is your best approach.
The other thing you could do is have your IGDBBackend service extend GDBackend which is probably
more change than overriding.
I suggest writing a bug to properly use IMIBackend for this.