[Issue 18536] New: Bad stack traces when building with -m32mscoff

[d-bugmail at puremagic.com]

https://issues.dlang.org/show_bug.cgi?id=18536

          Issue ID: 18536
           Summary: Bad stack traces when building with -m32mscoff
           Product: D
           Version: D2
          Hardware: x86
                OS: Windows
            Status: NEW
          Severity: normal
          Priority: P1
         Component: druntime
          Assignee: nobody at puremagic.com
          Reporter: r.sagitario at gmx.de

module stack;

void foo()
{
        throw new Exception("hi");
}

void main()
{
        foo();
}

compiled with "dmd -g -m32mscoff stack.d" and running the executable yields

object.Exception at stack.d(5): hi
----------------
0x002C1061 in stack
0x002C1078 in D at c:\tmp\d\stack.d(10)
0x002C161B in void rt.dmain2._d_run_main(int, char**, extern (C) int
function(char[][])*).runAll().__lambda1()
0x002C1599 in void rt.dmain2._d_run_main(int, char**, extern (C) int
function(char[][])*).runAll()
0x002C1430 in _d_run_main
0x002C1094 in __entrypoint
0x002F21EE in __tmainCRTStartup at f:\dd\vctools\crt\crtw32\startup\crt0.c(255)
0x770D8654 in BaseThreadInitThunk
0x77634A77 in RtlGetAppContainerNamedObjectPath
0x77634A47 in RtlGetAppContainerNamedObjectPath

Notice that the first entries just show the module name and "D" instead of "D
main".

--