Re: Memory leak with curl_multi_socket_action

On Tue, May 26, 2020 at 12:02 AM Jeffrey Walton <noloader_at_gmail.com> wrote:

> On Mon, May 25, 2020 at 6:27 PM James Read via curl-library
> <curl-library_at_cool.haxx.se> wrote:
> >
> > ...
> >
> > Gmail seems to have taken out all the formatting. Apologies. It should
> still compile though.
>
> I can't speak for others, but... You should probably reduce the code
> to a minimal reproducer, and then put it on GitHub or another place
> folks can 'git clone' and then 'make'.
>

git clone https://github.com/JamesRead5737/libcurlmemoryleak.git

No need to make. Just compile with gcc crawler.c -g -lssl -lcurl
Run valgrind with valgrind -v --tool=memcheck --leak-check=full
--show-reachable=yes --track-origins=yes --log-file=memcheck.log ./a.out

This should reproduce what I've been talking about.

James Read

>
> Jeff
>

-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2020-05-26