On Thursday, 14 January 2016 at 14:56:39 UTC, Byron Heads wrote:
std.net.curl.CurlException@std\net\curl.d(4033): Couldn't
resolve host name on handle 2188398
----------------
0x00405F65
0x00405F10
0x0040275B
0x0040259E
0x0040202B
0x00402035
0x004257A7
0x004256A8
0x0041B7FF
0x769F337A in BaseThreadInitThunk
0x77429882 in RtlInitializeExceptionChain
0x77429855 in RtlInitializeExceptionChain
This was a 4 hour debug which made it worse as I was adding
more trace calls to figure out what was going on. My boss is
now on the fence, to many compiler bugs with D, he asked me to
switch to Java if I have to deal to many more issues like
this.. (https://issues.dlang.org/show_bug.cgi?id=15457 another
issue we had)
And this awesome stack trace helped me so much to track this
issue down...
What compiler are you using?
The useless stack traces got fixed in a fairly recent version of
DMD - as have many, many other issues which are still present in
GDC, whose front end is several versions out-of-date.
It is recommended to do your testing with DMD because of issues
like this, and mostly use GDC for making optimized release builds.
Alternately, if you don't want to mix two compilers like that,
LDC has good performance and is currently significantly more
up-to-date than GDC. Or, you could even just use DMD, as the
performance of its generated binaries has improved a whole lot in
the past two releases, although it is of course still not as good
as GDC or LDC in this respect.
More generally, though, much as we might not like to admit it, D2
is still beta quality software. It is *vastly* more stable and
less frustrating to work with than it was a few years ago when I
first tried it, but it still has a long way to go before compiler
problems cease to be a part of normal day-to-day usage.
If that's not acceptable to you or your business, you really
probably should just use something else and check back in five
years or so...
