"Dima Tisnek" <dimaqq_at_gmail.com> wrote:

> Granted this is hardly an outright bug in pycurl, however I would
> rather like to track it down.

Agreed, I think the bug must be in libfaketime. Ask them.

> stack head:
> #0 0x0000000000000000 in ?? ()
> #1 0x00007ffff7bd9a3d in clock_gettime ()
> from /dima/libfaketime/src/libfaketime.so.1
> #2 0x00007ffff4702a13 in ?? () from /usr/lib/libcurl.so.4
> #3 0x00007ffff4703ca3 in ?? () from /usr/lib/libcurl.so.4
> #4 0x00007ffff47246d7 in ?? () from /usr/lib/libcurl.so.4
> #5 0x00007ffff4724f82 in ?? () from /usr/lib/libcurl.so.4
> #6 0x00007ffff495b4f2 in ?? () from /usr/lib/python2.7/site-packages/pycurl.so

I don't think you can blame anything of this on libcurl. AFAICS, libfaketime
intercepts user (i.e. libcurl) calls of time(), clock_gettime() etc to itself via some
trampoline or dynlibs hacks. I don't use Linux, but I'm sure libcurl cannot be
involved here. libcurl just trusts clock_gettime() to behave well.

--gv
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2012-04-04