On Tue, 24 May 2005, Michael Mastroianni wrote:

> I just built a version of this test on a linux box and ran it: I get EINVAL
> back from every single call to unlock.
>
> Still can't figure out what's causing it.

I don't see how libcurl has anything to do with problems to use thread-related
lock/unlock functions.

Here's an example of a working use of the share interface:

   http://curl.haxx.se/lxr/source/tests/libtest/lib506.c

This merely shows how it works, it doesn't actually perform any proper
locks/unlocks.

But it proves that the basic libcurl functionality for this works.

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