I'm not sure man, because it seems that it is only available for Linux. I'm leaning towards GDB (used with GDC on Windows) as it is well established, multiplatform and will definitely stay around for a while. I'm open for ZeroBugs though but I need a working Windows version which could be used against a DMD produced executable.

On 9 February 2012 17:10, Zachary Lund <admin@computerquip.com> wrote:
On Wednesday, 1 February 2012 at 22:05:16 UTC, Gyula Gubacsi wrote:
Thanks for your answer.

I am aware of the Visual D's solution for debugging but I'm actually
looking for a candidate debugger for integrating in to DDT, so these
solutions won't work for me.

On 1 February 2012 21:39, Rainer Schuetze <r.sagitario@gmx.de> wrote:
Hi,


On 01.02.2012 11:31, Gyula Gubacsi wrote:

Hi,

Can somebody update me on how the compiler/debugger implementations
are going on the 3 main platforms? What are you using, which is the
most useful for D applications? To my knowledge, the situation is like
this:
* Windows: DMD->  producing CodeView debug info format. ->  No GDB
support.
                  Old version of WinDBG is in the D bundle.
                 GDC ?


With the help of cv2pdb (http://dsource.org/projects/cv2pdb) the dmd
generated debug information can be converted to a pdb file, so you can use
most C++ debuggers including Visual Studio.
Visual D (http://www.dsource.org/projects/visuald) includes cv2pdb, but also
mago (http://dsource.org/projects/mago debugger). mago is a Visual Studio

debug engine that works directly on the dmd generated debug info, but still
misses some features of other debuggers.

There is also ddbg (http://ddbg.mainia.de/) which integrates with other
IDEs, but it is no longer updated. I don't know how well it works with
recent dmd releases.

The next Visual D/cv2pdb version will feature gdc support including
debugging (cv2pdb will convert the DWARF info to pdb).

Rainer

http://zerobugs.codeplex.com/

?