Am Thu, 14 Jan 2016 21:36:01 +0000 schrieb tsbockman <thomas.bock...@gmail.com>:
> 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. I'm not sure why you even think the OP is using GDC. His bug report says he's on windows 10. GDC is not supported on windows systems and won't work for anything but trivial programs. And stack traces is one thing GDC has had proper support way before DMD. We have proper stack traces since June 2013: https://github.com/D-Programming-GDC/GDC/pull/65 https://github.com/D-Programming-GDC/GDC/commit/fbde3698398f85768bcf918a7a777d81fd0ac3ed
