This newsgroup is for discussions about debuggers for D with at least some D specific support:

1) Cristi Vlasceanu's ZeroBUGS for Linux:

http://www.zerobugs.org/

2) Jascha Wetzel's Ddbg for Windows:

http://ddbg.mainia.de/releases.html

3) gdb modified to debug D:

http://www.gnu.org/software/gdb/gdb.html
http://svn.dsource.org/projects/gdb-patches/downloads/
http://sourceforge.net/project/showfiles.php?group_id=135857&package_id=223105

4) DigDug

http://www.dsource.org/projects/digdug/

5) Wiki

http://www.prowiki.org/wiki4d/wiki.cgi?DebugEnvironments

Walter Bright wrote:
> This newsgroup is for discussions about debuggers for D with at least some D specific support:
> 
> 1) Cristi Vlasceanu's ZeroBUGS for Linux:
> 
> http://www.zerobugs.org/

D support is still vapor as far as I know?  Couldn't find anything mentioned on the web page.

> 2) Jascha Wetzel's Ddbg for Windows:
> 
> http://ddbg.mainia.de/releases.html

Yeah!

> 3) gdb modified to debug D:
> 
> http://www.gnu.org/software/gdb/gdb.html
> http://svn.dsource.org/projects/gdb-patches/downloads/
> http://sourceforge.net/project/showfiles.php?group_id=135857&package_id=223105 
> 
> 
> 4) DigDug
> 
> http://www.dsource.org/projects/digdug/

Looks like vapor too.

> 5) Wiki
> 
> http://www.prowiki.org/wiki4d/wiki.cgi?DebugEnvironments


Don't forget everyone's favorite pre-bundled D-ready fully crash-enabled debugger for Windows
6) WinDbg!
   http://www.digitalmars.com/d/windbg.html

--bb

Honestly .. the only one that counts (at least as of now) is this:
http://ddbg.mainia.de/releases.html

Hasan Aljudy wrote:
> Honestly .. the only one that counts (at least as of now) is this:
> http://ddbg.mainia.de/releases.html
> 
> 
'Course, that doesn't mean we can't at least /talk/ about the other possibilities.  I suspect this newsgroup is intended more to be a place where it's ok to go back and forth ad infinitum about CODEVIEW esoterica  without worrying about annoying everyone on the main forum.

--bb

Bill Baxter wrote:

> Walter Bright wrote:
>> This newsgroup is for discussions about debuggers for D with at least some D specific support:
>> 
>> 1) Cristi Vlasceanu's ZeroBUGS for Linux:
>> 
>> http://www.zerobugs.org/
> 
> D support is still vapor as far as I know?  Couldn't find anything mentioned on the web page.
> 

He doesn't mention it on the website, but there is some limited support for D.  I've been working with it a bit today.

Unfortunately, when it comes to debugging D code on Linux it's hard to label a debugger as vaporware when in fact "dmd -g" is vaporware.  I can't tell what's the debugger's fault and what DMD either isn't doing or is doing wrong.  Hell, #146 is still open!  I'm pretty sure that a fair of the linenumber and file information is wrong, and most symbols don't appear in the DWARF information.  I don't mind sounding like a broken record when I say that I'd be very, very happy if the next DMD had real Linux debugging support.  According to Critian, it's not too hard to do with libdwarf.

-- 
~John Demme
me@teqdruid.com
http://www.teqdruid.com/

John Demme wrote:
> Bill Baxter wrote:
> 
>> Walter Bright wrote:
>>> This newsgroup is for discussions about debuggers for D with at least
>>> some D specific support:
>>>
>>> 1) Cristi Vlasceanu's ZeroBUGS for Linux:
>>>
>>> http://www.zerobugs.org/
>> D support is still vapor as far as I know?  Couldn't find anything
>> mentioned on the web page.
>>
> 
> He doesn't mention it on the website, but there is some limited support for
> D.  I've been working with it a bit today.
> 
> Unfortunately, when it comes to debugging D code on Linux it's hard to label
> a debugger as vaporware when in fact "dmd -g" is vaporware.  I can't tell
> what's the debugger's fault and what DMD either isn't doing or is doing
> wrong.  Hell, #146 is still open!  I'm pretty sure that a fair of the
> linenumber and file information is wrong, and most symbols don't appear in
> the DWARF information.  I don't mind sounding like a broken record when I
> say that I'd be very, very happy if the next DMD had real Linux debugging
> support.  According to Critian, it's not too hard to do with libdwarf.
> 
I am currently having an email exchange with Walter on the topic of line numbers. Which BTW, work with GDC.

Indeed, the only place I alluded to D is on the zero-bugs.com FAQ page. Thomas Kuehne has graciously contributed a D demangler, the Dmain function and the dthrow are detected, but that's about it so far.

I hope to get the D support in a better shape as soon as we fix this line numbers show stopper problem.

Bill Baxter Wrote:

> Walter Bright wrote:
> > This newsgroup is for discussions about debuggers for D with at least some D specific support:
> > 
> > 1) Cristi Vlasceanu's ZeroBUGS for Linux:
> > 
> > http://www.zerobugs.org/
> 
> D support is still vapor as far as I know?  Couldn't find anything mentioned on the web page.

I was about to ask about that.  It looks like a great debugger, but I didn't know it had D-specific support yet.

Howard

Hasan Aljudy wrote:
> Honestly .. the only one that counts (at least as of now) is this:
> http://ddbg.mainia.de/releases.html

As long as it's windows only, I don't see how you can say that.  I don't do any windows development and can't see doing any in the foreseeable future.

Later,
Brad

== Quote from Bill Baxter (dnewsgroup@billbaxter.com)'s article
> Walter Bright wrote:
> > This newsgroup is for discussions about debuggers for D with at least some D specific support:
> >
> > 1) Cristi Vlasceanu's ZeroBUGS for Linux:
> >
> > http://www.zerobugs.org/
> D support is still vapor as far as I know?  Couldn't find anything mentioned on the web page.

...

> > 4) DigDug
> >
> > http://www.dsource.org/projects/digdug/
> Looks like vapor too.

FWIW, DigDug is more "abandonware" than "vaporware".
(See http://www.dsource.org/forums/viewtopic.php?t=153)

And for the very curious, the code and a Windows binary are still available, too: http://svn.dsource.org/projects/digdug/

jcc7

John Demme wrote:
> I'm pretty sure that a fair of the
> linenumber and file information is wrong

Imagine when mixins will come into play. What line and number information can be recorded for symbols generated at compile time? :-O