Am 23.07.2017 um 03:35 schrieb Hugo D.:
On Sat, 22 Jul 2017 15:31:03 +0200, Sönke Ludwig wrote:
Just to rule this out, can you try if this also occurs with LDC 1.3.0
final? I remember there were some issues with the betas, although I
don't know if those were related.Still happens on ldc2 1.3.0 final.
Running with verbose debug logging spits out this stack trace, if it can be of any help.
Full error: core.exception.RangeError@C:\D\ldc2\bin\..\import\std\container\array.d(593): Range violation ---------------- 0x00007FF7E663CD08 in std.container.array.Array!(void*).Array.opSlice at C:\D\ldc2\import\std\container\array.d(593) 0x00007FF7E663C712 in vibe.core.drivers.libasync.LibasyncManualEvent.removeMySignal at [...]\vibe-d-0.8.0\vibe-d\core\vibe\core\drivers\libasync.d(969) (...)
Ah, you are using the libasync driver, which is currently not tested
against LDC, because of LDC specific failures. If possible, it would be
the safest bet to use a different compiler/driver combination for now.
But, without understanding the root cause for the error, I've committed
a fix for this particular range violation error and tagged version
0.8.1-alpha.4. The CI test now also passes on LDC 1.3.0.