Thread overview
[Issue 13227] DMD-Win64 debuginfo corruption
Sep 24, 2014
Manu
Dec 19, 2014
Walter Bright
Dec 20, 2014
Rainer Schuetze
Aug 20, 2019
Rainer Schuetze
September 24, 2014
https://issues.dlang.org/show_bug.cgi?id=13227

Manu <turkeyman@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |symdeb

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

Walter Bright <bugzilla@digitalmars.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bugzilla@digitalmars.com

--- Comment #1 from Walter Bright <bugzilla@digitalmars.com> ---
Can you isolate it down a bit? This can be done by turning debug info on/off for modules in the project in a binary search, narrowing it down to which module it is.

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

Rainer Schuetze <r.sagitario@gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |r.sagitario@gmx.de

--- Comment #2 from Rainer Schuetze <r.sagitario@gmx.de> ---
I compiled hello.d from luaD and it works for me with dmd 2.066.1 and git head (Win64 and Win32mscoff, debug and release).

Building a release version needs the -allinst option, though, and causes a luaError.

--
August 20, 2019
https://issues.dlang.org/show_bug.cgi?id=13227

Rainer Schuetze <r.sagitario@gmx.de> changed:

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

--- Comment #3 from Rainer Schuetze <r.sagitario@gmx.de> ---
I suspect this is no longer valid and wasn't reproducible to begin with. Please reopen with more info if the problem persists.

--