digitalmars.D.debugger - Debugger options
- Gyula Gubacsi <gyula.gubacsi gmail.com> Feb 01 2012
- Jacob Carlborg <doob me.com> Feb 01 2012
- Rainer Schuetze <r.sagitario gmx.de> Feb 01 2012
- Gyula Gubacsi <gyula.gubacsi gmail.com> Feb 01 2012
- "Zachary Lund" <admin computerquip.com> Feb 09 2012
- Gyula Gubacsi <gyula.gubacsi gmail.com> Feb 10 2012
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. =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Old version of WinDBG i= s in the D bundle. =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 GDC ? * Linux: DMD/GDC-> producing DWARF debug info format -> Very limited GDB support as GDB has no explicit D support. How does that work with the C style debug info? Is both GDC and DMD reliable on producing correct debug info? * Mac: I have no experience on this platform but the situation must be something similar to Linux. 32/64bit: Are there any limitation if the executable is 64bit? Could someone fill the gaps for me? Thanks Gyula Gubacsi
Feb 01 2012
Jacob Carlborg <doob me.com> On 2012-02-01 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 ? * Linux: DMD/GDC-> producing DWARF debug info format -> Very limited GDB support as GDB has no explicit D support. How does that work with the C style debug info? Is both GDC and DMD reliable on producing correct debug info? * Mac: I have no experience on this platform but the situation must be something similar to Linux. 32/64bit: Are there any limitation if the executable is 64bit?
GDB and DWARF is used on Mac OS X as well. 32/64bit is not a problem on Mac OS X, almost all libraries and tools are available in both 32 and 64bit variants. -- /Jacob Carlborg
Feb 01 2012
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
Feb 01 2012
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-> =A0producing CodeView debug info format. -> =A0No GDB support. =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Old version of WinDBG is in the D bu=
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0GDC ?
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 us=
most C++ debuggers including Visual Studio. Visual D (http://www.dsource.org/projects/visuald) includes cv2pdb, but a=
mago (http://dsource.org/projects/mago_debugger). mago is a Visual Studio debug engine that works directly on the dmd generated debug info, but sti=
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
Feb 01 2012
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/ ?
Feb 09 2012
--f46d04016a99d5c27d04b89bc01a Content-Type: text/plain; charset=ISO-8859-1 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<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<http://www.dsource.org/projects/visuald>) includes cv2pdb, but also mago (http://dsource.org/projects/**mago<http://dsource.org/proj cts/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
?
--f46d04016a99d5c27d04b89bc01a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 estab= lished, multiplatform and will definitely stay around for a while. I'm = open for ZeroBugs though but I need a working Windows version which could b= e used against a DMD produced executable.<br> <br><div class=3D"gmail_quote">On 9 February 2012 17:10, Zachary Lund <span= dir=3D"ltr"><<a href=3D"mailto:admin computerquip.com">admin computerqu= ip.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"= margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div class=3D"im">On Wednesday, 1 February 2012 at 22:05:16 UTC, Gyula Guba= csi wrote:<br> </div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l= eft:1px #ccc solid;padding-left:1ex"><div class=3D"im"> Thanks for your answer.<br> <br> I am aware of the Visual D's solution for debugging but I'm actuall= y<br> looking for a candidate debugger for integrating in to DDT, so these<br> solutions won't work for me.<br> <br> On 1 February 2012 21:39, Rainer Schuetze <<a href=3D"mailto:r.sagitario= gmx.de" target=3D"_blank">r.sagitario gmx.de</a>> wrote:<br> </div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l= eft:1px #ccc solid;padding-left:1ex"><div class=3D"im"> Hi,<br> <br> <br> On 01.02.2012 11:31, Gyula Gubacsi wrote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> <br> Hi,<br> <br> Can somebody update me on how the compiler/debugger implementations<br> are going on the 3 main platforms? What are you using, which is the<br> most useful for D applications? To my knowledge, the situation is like<br> this:<br> * Windows: DMD-> =A0producing CodeView debug info format. -> =A0No GD= B<br> support.<br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Old version of WinDBG is in the D bundl= e.<br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0GDC ?<br> </blockquote> <br> <br> With the help of cv2pdb (<a href=3D"http://dsource.org/projects/cv2pdb" tar= get=3D"_blank">http://dsource.org/projects/<u></u>cv2pdb</a>) the dmd<br> generated debug information can be converted to a pdb file, so you can use<= br> most C++ debuggers including Visual Studio.<br> Visual D (<a href=3D"http://www.dsource.org/projects/visuald" target=3D"_bl= ank">http://www.dsource.org/<u></u>projects/visuald</a>) includes cv2pdb, b= ut also<br></div> mago (<a href=3D"http://dsource.org/projects/mago" target=3D"_blank">http:/= /dsource.org/projects/<u></u>mago</a> debugger). mago is a Visual Studio<di= v class=3D"im"><br> debug engine that works directly on the dmd generated debug info, but still= <br> misses some features of other debuggers.<br> <br> There is also ddbg (<a href=3D"http://ddbg.mainia.de/" target=3D"_blank">ht= tp://ddbg.mainia.de/</a>) which integrates with other<br> IDEs, but it is no longer updated. I don't know how well it works with<= br> recent dmd releases.<br> <br> The next Visual D/cv2pdb version will feature gdc support including<br> debugging (cv2pdb will convert the DWARF info to pdb).<br> <br> Rainer<br> </div></blockquote></blockquote> <br> <a href=3D"http://zerobugs.codeplex.com/" target=3D"_blank">http://zerobugs= .codeplex.com/</a><br> <br> ?<br> </blockquote></div><br> --f46d04016a99d5c27d04b89bc01a--
Feb 10 2012