Bug 11368 – Couldn't Mago debugger be the default debugger engine?
Status
RESOLVED
Resolution
FIXED
Severity
enhancement
Priority
P2
Component
visuald
Product
D
Version
D2
Platform
All
OS
All
Creation time
2013-10-27T13:33:00Z
Last change time
2015-06-26T14:32:25Z
Assigned to
nobody
Creator
aliloko
Comments
Comment #0 by aliloko — 2013-10-27T13:33:06Z
When using VisualD, debugging with Mago is more often than not more correct than the other option.
Each time I generate a project with dub, I switch to Mago debugger.
This could be change in "dub generate", but not everyone has Mago + cv2pdb installed, and it would be cleaner to choose Mago as a default in VisualD.
What do you think?
Comment #1 by r.sagitario — 2013-10-28T23:49:58Z
I think mago is the way to go long term. But there are still a few things that are missing from mago to make it the default, most obviously 64-bit support. I would like to avoid having very different debugging experience on Win32 and x64.
The good news is: 64-bit support for mago is being worked on.
Comment #2 by doob — 2013-10-29T00:34:19Z
Isn't the Visual Studio debugger preferred when compiled 64bit?
Comment #3 by r.sagitario — 2013-10-29T00:44:51Z
The Visual Studio debug engine is the only working engine on x64 at the moment. You'll still have to live with some C++ syntax and need a patched dmd to generate sensible debug information, e.g. with respect to inspecting class member variables.