Re: Bug with latest curl and http://www.google.com/

On Mon, 4 Jun 2007, Daniel Stenberg wrote:

> Whoa, major badness. It seems to occur on adresses that return more than one
> IP to a request. I get the crash for this as well:

I nailed (and committed) the worst part of the valgrind report that caused the
crash, and I'm working on silencing the "Syscall param socketcall.send(msg)
points to uninitialised byte(s)" and "Conditional jump or move depends on
uninitialised value(s)" messages.

-- 
   c-ares -- my preferred DNS asynch resolver library