On Saturday, 19 September 2015 at 13:34:27 UTC, Guillaume
Chatelet wrote:
Is this a known issue ? Why Auto Tester didn't catch it ?
It's coming from d_do_test, gdb gives this stacktrace.
Program received signal SIGSEGV, Segmentation fault.
0x0000000000460b64 in rt.deh_win64_posix.terminate() ()
(gdb) bt
#0 0x0000000000460b64 in rt.deh_win64_posix.terminate() ()
#1 0x0000000000445578 in _d_throwc ()
#2 0x0000000000409a00 in
std.exception.bailOut!(Exception).bailOut(immutable(char)[],
ulong, const(char[])) ()
#3 0x000000000040997d in std.exception.enforce!(Exception,
bool).enforce(bool, lazy const(char)[], immutable(char)[], ulong)
()
#4 0x000000000044ef7b in
std.stdio.File.LockingTextWriter.this(ref std.stdio.File) ()
#5 0x000000000044f080 in std.stdio.File.lockingTextWriter() ()
#6 0x000000000040771e in
std.stdio.File.write!(immutable(char)[]).write(immutable(char)[])
()
#7 0x000000000040769e in
std.stdio.write!(immutable(char)[]).write(immutable(char)[]) ()
#8 0x0000000000402d0e in d_do_test.usage() ()
#9 0x000000000040575c in D main ()
hmm so it's probably coming from druntime or phobos not being
build with the correct dmd version...
