Closed MartinNowak closed 7 years ago
Any details regarding the other dependencies or usage?
Also, build "versions" tags, did you try DisableDebugger
or EnableDebugger
? Is this a core dump or a gdb debugging session / reproducible?
Do you use concurrency? Which curves are you using?
Try removing the name append here: https://github.com/etcimon/botan/blob/v1.12.7/source/botan/tls/extensions.d#L790 which could have been deserialized as null maybe?
The stack trace is fairly broken in gdb, so it might not even be a regular call.
Here is the stracktrace from the exception http://pastebin.com/p4qaWEbA.
Did you provide a custom curve list? Which DMD version does this run with?
No, I did not, seems like policy.allowedEccCurves()
get's broken.
import std.stdio;
auto curves = policy.allowedEccCurves();
foreach (c; curves)
writeln("allowedEccCurves: ", c);
It's dmd 2.071.2.
Ok with that info I'll attempt to update my DMD version tomorrow and reproduce
Ok with that info I'll attempt to update my DMD version tomorrow and reproduce
I can recommend curl -fsS https://dlang.org/install.sh | bash -s dmd-2.071.2
;).
I decided to test run everything with 2.072.0, lots of regressions and errors. I couldn't get the same error but I can downgrade to 2.071.2 to see
Seems like the error happens in vibe.d filling it's CustomTLSPolicy, can take care of the rest of debugging.
Always end up in
botan.tls.extensions.SupportedEllipticCurves.nameToCurveId
w/ no arguments and a broken stack trace. I'd guess because of some memory corruption.