October 30, 2013 It seems LDC 12.0 on win32 has some problems with std.datetime | ||||
|---|---|---|---|---|
| ||||
Bascially there's no way to use the std.datetime module without getting an error on exit.
Very easy to reproduce:
import std.datetime;
int main(string[] args)
{
}
Compile and run this program in the console window. It prints out one line of error message on exit:
object.Exception@N:/Build/src/ldc/runtime/phobos/std/internal/windows/advapi32.d(65): FreeLibrary(hAdvapi32)
If we add the std.parallelism module, it gets worse:
import std.parallelism;
import std.datetime;
int main(string[] args)
{
}
Now on exit, it pops up an error dialog:
"The instruction at 0x77c5f766 referenced memory at 0x00000018. The memory could not be read.
Click on OK to terminate the program"
| ||||
October 30, 2013 Re: It seems LDC 12.0 on win32 has some problems with std.datetime | ||||
|---|---|---|---|---|
| ||||
Posted in reply to finalpatch | This is due to using an incompatible (newer) version of MinGW-w64 with LCD. Download the version linked in the README.txt file and then works fine.
On Wednesday, 30 October 2013 at 11:07:17 UTC, finalpatch wrote:
> Bascially there's no way to use the std.datetime module without getting an error on exit.
>
> Very easy to reproduce:
>
> import std.datetime;
> int main(string[] args)
> {
> }
>
> Compile and run this program in the console window. It prints out one line of error message on exit:
>
> object.Exception@N:/Build/src/ldc/runtime/phobos/std/internal/windows/advapi32.d(65): FreeLibrary(hAdvapi32)
>
> If we add the std.parallelism module, it gets worse:
>
> import std.parallelism;
> import std.datetime;
> int main(string[] args)
> {
> }
>
> Now on exit, it pops up an error dialog:
>
> "The instruction at 0x77c5f766 referenced memory at 0x00000018. The memory could not be read.
>
> Click on OK to terminate the program"
| |||
Copyright © 1999-2021 by the D Language Foundation
Permalink
Reply