On Tue, 5 May 2009, ameya agnihotri wrote:

> Following is the scenario:

...

> 1. Is the above usage valid for libcurl on linux?

I think so. It wasn't crystal clear in every aspect, but it looked fine.

> 2. Is there any restriction on calling curl_easy_setopt() , after
> curl_multi_perform() ?

Not that I can think of.

> Following is the back trace obtained from coredump using gdb:
> #0 0x00b4c7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
> #1 0x00b927a5 in raise () from /lib/tls/libc.so.6
> #2 0x00b94209 in abort () from /lib/tls/libc.so.6
> #3 0x00bc6a1a in __libc_message () from /lib/tls/libc.so.6
> #4 0x00bcd2bf in _int_free () from /lib/tls/libc.so.6
> #5 0x00bcd63a in free () from /lib/tls/libc.so.6
> #6 0x0060dd74 in setstropt () from /usr/local/lib/libcurl.so.4
> #7 0x0060f8ea in Curl_setopt () from /usr/local/lib/libcurl.so.4
> #8 0x0061f06b in curl_easy_setopt () from /usr/local/lib/libcurl.so.4

Rebuild with debug enabled to catch more symbols/details.

Does it crash on the same spot every time? What particular setopt is it doing
then?

Any chance you can reproduce this crash with a smallish example we can try?

> curl 7.19.2 (i686-pc-linux-gnu)

Have you tried with 7.19.4 to see if the problem remains?

-- 
  / daniel.haxx.se