On Thu, 7 May 2009, Jon Smirl wrote:
It's doing a fetch of a remote http server...
I hit this once. Then ran the gdb and hit it again.
I installed libcurl3-dbg and was unable to get it to reproduce again after
that.
[...]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f2b89134710 (LWP 22527)]
0x00007f2b88d299d0 in ?? () from /usr/lib/libcurl.so.4
(gdb) bt
#0 0x00007f2b88d299d0 in ?? () from /usr/lib/libcurl.so.4
#1 0x00007f2b88d2a55c in ?? () from /usr/lib/libcurl.so.4
#2 0x00007f2b88d2a762 in ?? () from /usr/lib/libcurl.so.4
#3 0x00007f2b88d2b24b in curl_multi_perform () from /usr/lib/libcurl.so.4
This really is too few details to work with. curl_multi_perform() is the entry
point to a lot of code so without better pinpointing to exactly what failed
this is next to impossible for me to guess.
Note also that we've done a few more releases from the curl project since
7.18.2 so you may suffer from an already fixed bug.
--
/ daniel.haxx.se
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html