strtr wrote:
BCS Wrote:
Hello Strtr,
If you can try it on linux it's not to hard to build a debug version of dmd
and run it under the debugger. That will at least give you a filename/line
number for the bug report and with a little thinking and a stack trace you
can take a guess at what code is causing the failure. I guess the same things
can be done on windows (using windbg) but I've never done it there.
--
<IXOYE><
I didn't even know it was possible to build dmd :)
Starting with versions 1.041 and 2.026, the DMD source code is included
in the zip file. :)
-Lars
