On Fri, 10 May 2013, Raheman Vaiya wrote:
I think there is a memory leak in the curl code. Running valgrind on the
following code (first link) yields the output in the second link. Since this
is my first time attempting debugging "real" code I may have made some
trivial mistake, if this is the
On Fri, May 10, 2013 at 9:51 AM, Raheman Vaiya wrote:
> I think there is a memory leak in the curl code. Running valgrind on the
> following code (first link) yields the output in the second link. Since this
> is my first time attempting debugging "real" code I may have made some
> trivial mistake
Hello,
I think there is a memory leak in the curl code. Running valgrind on the
following code (first link) yields the output in the second link. Since
this is my first time attempting debugging "real" code I may have made some
trivial mistake, if this is the case please let me know, I would great
On Wed, May 8, 2013 at 5:40 AM, Daniel Stenberg wrote:
> On Tue, 7 May 2013, Alex Loukissas wrote:
>
> Yes rather strange behavior, although it's not very frequent. Do you
>> perhaps have a hunch on anything I might have missed in the way I'm using
>> curl_multi interface?
>>
>
> Nothing you can
Trying to build curl for WIN64 but run into some problems:
I got warnings about redefinitions of fstat/stat.
I could fix those by adding the follow lines to curl_setup.h:371 and
curl_setup.h:388
# undef fstat
# undef stat
The second problem is that I am unable to build the shared version of cu
I have just tested your fix using the latest git master and can confirm the
crash is gone.
Thanks!
On Wed, May 8, 2013 at 11:18 PM, Marc Hoersken wrote:
> 2013/5/7 Daniel Stenberg :
> > Just to clarify: we can close #1219 now then?
> >
> > https://sourceforge.net/p/curl/bugs/1219/
>
> Yes, sinc
