On Thu, Mar 22, 2007 at 04:51:23PM -0700, Mark Wattier wrote:
> We have a set of wrappers for curl that we have been using in our
> application for a long time, but it always would only make one access
> in the life of a process. We are now doing something fancier,
> involving multiple accesses, and we get this particular problem with
> the third access attempt. The program goes into curl_easy_perform, and
> never comes out, using 20% of the CPU or more. I kill the process with
> signal 11, and it always appears to be in the same place. See core
> dump below.

It looks like the heap has been corrupted somehow. How are you
implementing these "multiple accesses"? Multithreading? Have you taken
care of all the locking issues?

>>> Dan

-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved