Hi all,

cv2pdb is a converter of DMD CodeView debug information to PDB debug format to make debugging of D applications that were created with the DMD compiler, as seamless as possible in current versions of Visual Studio (i.e Visual Studio 2008 and VCExpress).

Major Features:

    * conversion of DMD CodeView information to PDB file
    * converted line number info allows setting breakpoints
    * display of variables, fields and objects in watch, local
      and auto window and in data tooltips
    * convenient display of dynamic and associative arrays
      in watch windows
    * demangles function names for convenient display of callstack

Version 0.1 is available now at

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

Enjoy,
Rainer Schuetze

On Sat, 09 May 2009 12:27:39 +0400, Rainer Schuetze <r.sagitario@gmx.de> wrote:

> Hi all,
>
> cv2pdb is a converter of DMD CodeView debug information to PDB debug format to make debugging of D applications that were created with the DMD compiler, as seamless as possible in current versions of Visual Studio (i.e Visual Studio 2008 and VCExpress).
>
> Major Features:
>
>      * conversion of DMD CodeView information to PDB file
>      * converted line number info allows setting breakpoints
>      * display of variables, fields and objects in watch, local
>        and auto window and in data tooltips
>      * convenient display of dynamic and associative arrays
>        in watch windows
>      * demangles function names for convenient display of callstack
>
> Version 0.1 is available now at
>
>      http://www.dsource.org/projects/cv2pdb
>
> Enjoy,
> Rainer Schuetze

Wow, that's good news! Thank you!

在 Sat, 09 May 2009 16:27:39 +0800，Rainer Schuetze <r.sagitario@gmx.de> 写道:

> Hi all,
>
> cv2pdb is a converter of DMD CodeView debug information to PDB debug format to make debugging of D applications that were created with the DMD compiler, as seamless as possible in current versions of Visual Studio (i.e Visual Studio 2008 and VCExpress).
>
> Major Features:
>
>      * conversion of DMD CodeView information to PDB file
>      * converted line number info allows setting breakpoints
>      * display of variables, fields and objects in watch, local
>        and auto window and in data tooltips
>      * convenient display of dynamic and associative arrays
>        in watch windows
>      * demangles function names for convenient display of callstack
>
> Version 0.1 is available now at
>
>      http://www.dsource.org/projects/cv2pdb
>
> Enjoy,
> Rainer Schuetze

thanks for the great job!

-- 
使用 Opera 革命性的电子邮件客户程序: http://www.opera.com/mail/

On Sat, 09 May 2009 11:27:39 +0300, Rainer Schuetze <r.sagitario@gmx.de> wrote:

> cv2pdb is a converter of DMD CodeView debug information to PDB debug format to make debugging of D applications that were created with the DMD compiler, as seamless as possible in current versions of Visual Studio (i.e Visual Studio 2008 and VCExpress).

Awesome! (Although I believe Visual Studio already has limited support for CV debug information...)

A question: do you think it's possible to strip the CV debug info from the executable while preserving compatibility with the PDB? I ask this because this would make it possible to do remote debugging and post-mortem (crash dump) analysis with closed-source applications (which can't have debug information in the release executables).

-- 
Best regards,
 Vladimir                          mailto:thecybershadow@gmail.com

Vladimir Panteleev wrote:
> On Sat, 09 May 2009 11:27:39 +0300, Rainer Schuetze <r.sagitario@gmx.de> wrote:
> 
>> cv2pdb is a converter of DMD CodeView debug information to PDB debug format to make debugging of D applications that were created with the DMD compiler, as seamless as possible in current versions of Visual Studio (i.e Visual Studio 2008 and VCExpress).
> 
> Awesome! (Although I believe Visual Studio already has limited support for CV debug information...)

Yes, debugging in VS "almost" works for standard DMD debug info, but with two major drawbacks: you cannot set breakpoints (stepping through the code works, though) and class members are not shown correctly.
When looking at the details there are some more quirks.

> 
> A question: do you think it's possible to strip the CV debug info from the executable while preserving compatibility with the PDB? I ask this because this would make it possible to do remote debugging and post-mortem (crash dump) analysis with closed-source applications (which can't have debug information in the release executables).
> 

That should not be a big problem. The current implementation renames the DMD debug section. Throwing it out needs some more modifications to the executable, but not a lot.

Rainer

Sweet! Thanks :D


-- 
Tomasz Stachowiak
http://h3.team0xf.com/
h3/h3r3tic on #D freenode

On Sat, 09 May 2009 10:27:39 +0200, Rainer Schuetze <r.sagitario@gmx.de> wrote:

> cv2pdb is a converter of DMD CodeView debug information to PDB debug format to make debugging of D applications that were created with the DMD compiler, as seamless as possible in current versions of Visual Studio (i.e Visual Studio 2008 and VCExpress).

Hi, that's pretty cool.

One question: Does this tool work with DMC files as well? Even we all now use D, using a C compiler sometimes is still rwequired ;-).

-- 
Robert M. Münch
Management & IT Freelancer
http://www.robertmuench.de

Hi,

Robert M. Münch wrote:
> On Sat, 09 May 2009 10:27:39 +0200, Rainer Schuetze <r.sagitario@gmx.de> wrote:
> 
>> cv2pdb is a converter of DMD CodeView debug information to PDB debug format to make debugging of D applications that were created with the DMD compiler, as seamless as possible in current versions of Visual Studio (i.e Visual Studio 2008 and VCExpress).
> 
> Hi, that's pretty cool.
> 
> One question: Does this tool work with DMC files as well? Even we all now use D, using a C compiler sometimes is still rwequired ;-).
> 

I just tried to convert the compiled DMD code, but that produced an error "dmd.exe: unsupported field entry". A dump showed that there are a few debug entries that don't seem to occur in D code, and that the line numbers are wrong.

So, sorry, no simple cure for that problem.

Rainer