Hi Daniel,

I have provided the stack trace below. Like I mentioned before, I have over
100 files in the directory and I try to "GET" each of those and process
them. So it is a for-loop that changes the url to be accessed to the next
filename and issues a curl_perform. Things work okay for like 20 or so files
and then I almost consistently get this SIGSEGV (on 7.9.8v)

From the stack trace it looks like it is accessing a string that is not good
(either bad heap or not properly terminated). The same piece of code seems
to behave okay with 7.10.3v. I just want to confirm that this is in fact a
bug and it has been fixed.

Here is the stack trace that I get.=============

#0 0x4207a4cb in strlen () from /lib/i686/libc.so.6

#1 0x406fe8be in dprintf_formatf () from /usr/lib/libcurl.so.2

#2 0x406ff07a in curl_mvsnprintf () from /usr/lib/libcurl.so.2

#3 0x406f40aa in Curl_infof () from /usr/lib/libcurl.so.2

#4 0x406f87cf in verboseconnect () from /usr/lib/libcurl.so.2

#5 0x406f921d in CreateConnection () from /usr/lib/libcurl.so.2

#6 0x406fa2cc in Curl_connect () from /usr/lib/libcurl.so.2

#7 0x4070339f in Curl_perform () from /usr/lib/libcurl.so.2

#8 0x40703ad8 in curl_easy_perform () from /usr/lib/libcurl.so.2

 End trace =============================

Thank you for the quick response.

- Uday

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Received on 2003-03-10