Thread overview
[Issue 11902] DMD debuginfo doesn't seem to write classes correctly
Dec 19, 2014
Walter Bright
Dec 19, 2014
Walter Bright
Dec 21, 2014
Manu
Dec 21, 2014
Rainer Schuetze
December 19, 2014
https://issues.dlang.org/show_bug.cgi?id=11902

Walter Bright <bugzilla@digitalmars.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--
December 19, 2014
https://issues.dlang.org/show_bug.cgi?id=11902

--- Comment #13 from Walter Bright <bugzilla@digitalmars.com> ---
(In reply to Manu from comment #12)
> (In reply to comment #11)
> > https://github.com/D-Programming-Language/dmd/pull/3189
> > 
> > I honestly don't think that my two pull requests will make it in time for 2.065, especially as 2.065 is already in the release canidate phase.
> 
> Yeah. That's a shame. I think this is pretty critical.

3189 was merged on Apr 7.

--
December 21, 2014
https://issues.dlang.org/show_bug.cgi?id=11902

--- Comment #14 from Manu <turkeyman@gmail.com> ---
Thanks walter!

Rainer: Is it possible to make VisualD manage this build flag appropriately according to the version of VisualStudio (or perhaps, which debug engine) the user is running?

--
December 21, 2014
https://issues.dlang.org/show_bug.cgi?id=11902

--- Comment #15 from Rainer Schuetze <r.sagitario@gmx.de> ---
The "debug info" selector has "Symbolic (suitable for Mago)" and "Symbolic (suitable for VS debug engine)". It could be derived from the selected debug engine, it already does that when determining whether to run cv2pdb or not. Unfortunately, this falls short when building libraries as the actually used debug engine isn't known then.

I was thinking of another option "suitable for selected debug engine" to cover the most common cases.

--