curl-and-php
Re: segfault, glibc corruption, redhat
Date: Thu, 4 Sep 2008 22:53:59 +0200 (CEST)
On Thu, 4 Sep 2008, Jon Drukman wrote:
> I'm not much of a gdb expert but I did manage to trigger a segfault and get
> a backtrace. Does this tell you anything useful?
You seem to have built parts of this with optimize options (like -O2) which
does ruin some of the ability to see all details.
> 0x0000003977c61cda in fwrite () from /lib64/libc.so.6
> (gdb) bt
> #0 0x0000003977c61cda in fwrite () from /lib64/libc.so.6
> #1 0x00002b98d031d6d4 in showit (data=0x12661680, type=<value optimized
> out>,
> ptr=0x7fffe0311330 "About to connect() to gdata.youtube.com port 80
> (#0)\n", size=53) at sendf.c:679
> #2 0x00002b98d031d766 in Curl_debug (data=0x12661680, type=CURLINFO_TEXT,
> ptr=0x7fffe0311330 "About to connect() to gdata.youtube.com port 80
> (#0)\n", size=53, conn=0x2b98cb025c50)
> at sendf.c:726
So this is the DEBUGFUNCTION option in libcurl that somehow crashes when it
calles fwrite().
I would guess on some sort of memory corruption.
-- / daniel.haxx.se _______________________________________________ http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-and-phpReceived on 2008-09-04