On Wed, 10 Jan 2007, Rom Walton wrote:

> I should point out that as far as I am aware, this is only happening on
> Windows. This call stack below was generated by our client software that
> was using libCurl 7.15.3, our current generation of software uses 7.15.5. We
> still see this crash on our latest clients, but so far none of the clients
> have returned a complete stack trace(clients were unable to download the
> symbol files for some reason).

> Have you all seen this issue before? Is it fixed in 7.16.0?

No, I can't recall having seen it before and I therefore don't think it is
fixed in 7.16.0 (although a memset size error was fixed in the win32 threaded
resolver) nor afterwards.

It would be interesting if you built a custom version of libcurl with the
"normal" resolver instead of the threaded one just to attempt to pinpoint
where the problem might be. That's the one major difference between windows
and other operating systems in the name resolving department that I can think
of right now.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html