On Sat, 8 Feb 2003, Todd Fisher wrote:

> here's the stack trace i'm getting from the core file
>
> #0 Curl_failf (data=0x0, fmt=0x4144a564 "\231\231\231\031
> Ø\036@\006\001") at sendf.c:153
> 153 if(data->set.errorbuffer && !data->state.errorbuf) {
> (gdb) where
> #0 Curl_failf (data=0x0, fmt=0x4144a564 "\231\231\231\031
> Ø\036@\006\001") at sendf.c:153
> #1 0x4003c106 in Curl_resolv (data=0x0, hostname=0x0, port=0) at
> hostip.c:237
> Current language: auto; currently c

No more frames?

The call to Curl_resolv() is obviously using completely broken parameters, so
whoever is using that like this is causing this problem.

Your fix may correct Curl_failf() to stop crashing, but it'll only move the
problem elsewhere. The reason for the problem would be found in frame #2 that
your stack trace above didn't show, for some reason.

(Now, I'm off for skiing!)

-- 
 Daniel Stenberg -- curl, cURL, Curl, CURL. Groks URLs.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld http://www.vasoftware.com