On Mon, 6 Aug 2001 brage_at_martzagency.com wrote:

> same EXACT libraries! (cept different compile times of course)
>
> Any idea which of the libraries used may be at fault?
>
> any help would be greatly appreciated!
>
> Slackware
> ---------
> root_at_web1:~# ldd /usr/local/bin/curl
> libcurl.so.1 => /usr/local/lib/libcurl.so.1 (0x40014000)
> libdl.so.2 => /lib/libdl.so.2 (0x400dd000)
> libc.so.6 => /lib/libc.so.6 (0x400e0000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
>
> Works FINE...
>
> Mandrake 8.0
> -------------
> [root_at_web2 curl-7.8]# ldd /usr/local/bin/curl
> libcurl.so.1 => /usr/local/lib/libcurl.so.1 (0x40017000)
> libdl.so.2 => /lib/libdl.so.2 (0x400e4000)
> libc.so.6 => /lib/libc.so.6 (0x400e8000)

We can see differences here, the libdl and libc are both different than the
slackware versions...

> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

> Ideas anyone? Daniel?

I really don't know.

I can't see any other solution than to single-step through the code and see
why the mandrake version breaks out from its download loop like that. It is
utterly weird.

There is another issue that has to do with how curl uses SSL_read() that
*could* be an item to check out. I've been reading the book "SSL and TLS -
Designing And Building Secure Systems" by Eric Rescorla lately, and it does
suggest that the way we use SSL_read() is flawed. I'm not very close to
addressing this right now though, but if nothing else proves to work, we
could make a dirty patch later on to verify that this is not the problem.
(The "solution" would be to repeat SSL_read() until SSL_pending() returns
FALSE.)

-- 
     Daniel Stenberg -- curl dude -- http://curl.haxx.se/
_______________________________________________
Curl-and-php mailing list
http://curl.haxx.se/