mago-mi: GDB/MI compatible frontend for Mago debugger

[Vadim Lopatin via Digitalmars-d-announce]

On Friday, 20 May 2016 at 03:15:46 UTC, E.S. Quinn wrote:
>> I also don't know which MI commands need to be supported to 
>> have it work with DDT. The thing is I didn't write the GDB 
>> debugger integration for DDT, I just reused the one from CDT. 
>> So I'm not that familiar with those internals.
>>
>> BTW, the MI integration is fairly language agnostic, so in 
>> theory your debugger could be used by CDT to debug C/C++ 
>> programs too, no? At least those generated by DMC. Maybe 
>> Visual Studio ones too?
>
> I'm experimenting with the build of mago-mi that comes with the 
> current ~master for dlangide, and it seems to throw an 
> unrecognized parameter error when on the --log-level=TRACE 
> parameter.
>
> And it seems that the version string it returns upsets eclipse, 
> as it throws the following error:
>
>  Could not determine GDB version using command: 
> D:\WinHome\<redacted>\AppData\Roaming\dub\packages\dlangide-master\bin\mago-mi.exe --version
>  Unexpected output format:
>
>  mago-mi debugger v0.1
>
>
> Though, from my experience using it in Linux, eclipse-CDT's 
> debugger seems pretty full-featured; it will likely require 
> large swaths of mi functionality to be fully useful.

I've fixed some CDT incompatibilities.
Now it's possible to start debugging program from Eclipse/DDT, 
set breakpoints, start execution.
Execution is stopped on breakpoint, but Eclipse does not see that 
program is stopped - does not enable step buttons, does not try 
to fetch current threads/frames/variables.
I see no visible difference between GDBs and mago-mi responses to 
commands.

Binaries can be downloaded here:
https://github.com/buggins/dlangide/releases/tag/v0.6.4

Now logs are forced, and written to mago-mi-debug.log file in the 
same directory where mago-mi.exe is located.