Debuggers for D

[Walter Bright]

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

[Bill Baxter]

Post by Walter Bright
This newsgroup is for discussions about debuggers for D with at least
http://www.zerobugs.org/

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

Post by Walter Bright
http://ddbg.mainia.de/releases.html

Yeah!

Post by Walter Bright
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.

Post by Walter Bright
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

[Hasan Aljudy]

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

[Bill Baxter]

Post by Walter Bright
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

[Brad Roberts]

Post by Walter Bright
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

[John Demme]

Post by Bill Baxter

Post by Walter Bright
This newsgroup is for discussions about debuggers for D with at least
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.

[Cristian Vlasceanu]

Post by John Demme

Post by Bill Baxter

Post by Walter Bright
This newsgroup is for discussions about debuggers for D with at least
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.

[John Demme]

Post by Cristian Vlasceanu

Post by John Demme

Post by Bill Baxter

Post by Walter Bright
This newsgroup is for discussions about debuggers for D with at least
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.

Great!

While you're at it, and Walter's knee deep in DWARF output, can you nudge
him in the direction of fixing bug #146? If you're doing any template
programming--and I do a--it's a debugging show stopper, also.

Thanks for your work with D!

[Ary Manzana]

Post by John Demme
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

[Jascha Wetzel]

it wouldn't make any sense to assign any line other than the one of the
mixin statement. hence this isn't much of a problem.

DMD for windows assigns the line following the mixin statement to the
code. well, kind of... it looks a bit like the current behaviour is not
intended.

Post by Ary Manzana

Post by John Demme
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

[Michael Coupland]

In an ideal world there would also be a full "stack trace" of
information where the mixin was used... The more complex metaprogramming
becomes, the more important it is to be able to (easily!) debug the
compilation process itself.

I don't pay too close attention to the D community, and clearly runtime
debugging support is a higher priority, but is
mixin/template/metaprogramming debugging on anyone's radar at all? It's
nice to have powerful metaprogramming support in D, but if the only way
to debug a wacky template is via compiler error messages, it's just as
bad as having to debug a normal program only using crash stack traces.

Post by Jascha Wetzel
it wouldn't make any sense to assign any line other than the one of the
mixin statement. hence this isn't much of a problem.
DMD for windows assigns the line following the mixin statement to the
code. well, kind of... it looks a bit like the current behaviour is not
intended.

Post by Ary Manzana

Post by John Demme
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

[Ary Borenszweig]

Post by Michael Coupland
In an ideal world there would also be a full "stack trace" of
information where the mixin was used... The more complex metaprogramming
becomes, the more important it is to be able to (easily!) debug the
compilation process itself.
I don't pay too close attention to the D community, and clearly runtime
debugging support is a higher priority, but is
mixin/template/metaprogramming debugging on anyone's radar at all?

Descent could do this in a future. I think it isn't hard, but it'll take
its time.

[Howard Berkey]

Post by Bill Baxter

Post by Walter Bright
This newsgroup is for discussions about debuggers for D with at least
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

[Howard Berkey]

Post by Bill Baxter

Post by Walter Bright
This newsgroup is for discussions about debuggers for D with at least
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

[jcc7]

== Quote from Bill Baxter (dnewsgroup at billbaxter.com)'s article

Post by Bill Baxter

Post by Walter Bright
This newsgroup is for discussions about debuggers for D with at
http://www.zerobugs.org/

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

...

Post by Bill Baxter

Post by Walter Bright
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