Re: [RFA] set debug mi

[Vladimir Prus <ghost at cs dot msu dot su>]

Michael Snyder wrote:

> On Wed, 2007-04-11 at 17:42 -0700, Jason Molenda wrote:
>> On Apr 11, 2007, at 4:50 PM, Michael Snyder wrote:
>> 
>> > Anybody think this is useful?
>> 
>> We do something similar at Apple but we have our front-end program
>> deal with it.  The UI has a preference to save the mi log to a file;
>> it saves all communication between gdb and the FE to that file.  It's
>> invaluable for debugging bug reports - it's invariably the first thing
>> we ask for when someone reports a bug against our debugger.  Besides
>> pointing the finger at either gdb or the front-end it has the benefit
>> of showing exactly what commands were sent to the debugger, instead of
>> relying on the user's memory of the same.
>> 
>> I think the approach of having all I/O between the debugger and the FE
>> saved is superior but having something like this built in to gdb could
>> be helpful for people who can't do that easily in the FE.
> 
> Eclipse also has a similar option.  I just thought it might be
> handy to have the facility on the gdb end as well.  By obvious
> analogy with "debug remote".

And KDevelop too. But I think this is better to be done in frontend. Frontend
would probably want to have logs of all debugger interaction shown to the user,
including CLI commands, so having a log file with just MI commands somewhere
won't help.

- Volodya