You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Compiled with LLVM ~master and LDC ~master on Win64, the resulting binary will crash with very little debugging information. Debugging with MS Visual Studio is close to useless, as the location of the crash seems unrelated to isFile() or main().
The following information is printed to the console after the crash: _d_throw_exception: RtlRaiseException failed. Perhaps this is the root of the problem (as I've experienced other crashes with similar symptoms as this, where the binary will simply crash and the stack trace will be near useless).
Building and running the same program with DMD:
$ dmd ldcio.d && ldcio.exe
std.file.FileException@std\file.d(922): testfile.tmp: The system cannot find the file specified.
----------------
0x004050BD
0x0040708C
0x004070C7
0x00406CC5
0x00405614
0x750B33AA in BaseThreadInitThunk
0x77379F72 in RtlInitializeExceptionChain
0x77379F45 in RtlInitializeExceptionChain
results in much more useful error message.
The text was updated successfully, but these errors were encountered:
This is a Win64-only issue (the example works on MinGW/Win32). As you said, it is probably related to a problem in the exception handling implementation; Win64 SEH in LLVM is still worked on. (@redstar, assigning to you)
Compiled with LLVM
~master
and LDC~master
on Win64, the resulting binary will crash with very little debugging information. Debugging with MS Visual Studio is close to useless, as the location of the crash seems unrelated to isFile() or main().The following information is printed to the console after the crash:
_d_throw_exception: RtlRaiseException failed
. Perhaps this is the root of the problem (as I've experienced other crashes with similar symptoms as this, where the binary will simply crash and the stack trace will be near useless).Building and running the same program with DMD:
results in much more useful error message.
The text was updated successfully, but these errors were encountered: