Win32: How to get the stack trace when compiling with a windows subsystem?

[Andrej Mitrovic]

On 8/19/13, Andrej Mitrovic <andrej.mitrovich at gmail.com> wrote:
> Thinking about it some more I think the .info field is empty because
> there's nothing really to trace, if I write the whole exception via
> writeln(thr) rather than writeln(thr.info), I'll get back the
> file+line of the failed assert, which should be enough for a module
> constructor (the Druntime function which ends up calling the actual
> module ctors isn't really important here).

Nevermind, I was printing out the wrong file, there really is some
kind of bug here. Anyway I'll file a small test-case to bugzilla.