On Sun, May 24, 2020 at 5:43 PM James Read <jamesread5...@gmail.com> wrote:
> > > On Sun, May 24, 2020 at 4:47 PM James Read <jamesread5...@gmail.com> > wrote: > >> >> >> On Sun, May 24, 2020 at 4:07 PM Daniel Stenberg <dan...@haxx.se> wrote: >> >>> On Sun, 24 May 2020, James Read via curl-library wrote: >>> >>> > Valgrind reports a memory leak in my web crawler: >>> >>> ... >>> >>> > What is memory being allocated for? >>> >>> Since your stack trace has no debug symbols it is hard for us to tell >>> exactyl >>> what's going on here. >>> >> >> OK >> >> >>> >>> > What do I need to free? >>> >>> If you use the libcurl API as documented, there should be nothing else >>> to >>> free. >>> >>> > Is this a bug in curl or is something wrong at my end? >>> >>> I can't tell because there's not enough information. I would prefer a >>> stand-alone source code that can reproduce the problem or if that's too >>> hard, >>> maybe you could at least run a debug-version of libcurl with the symbols >>> present so that we can see a more descriptive stack trace there? >>> >>> >> How do I do that? I'm on ubuntu using packages. I guess this would mean >> installing from source with some special flags? >> > > I compiled from source with ./configure --enable-debug I reran in valgrind > but the stack traces still seem to be missing the debug symbols. What am I > doing wrong here? > On closer inspection my valgrind output has the following lines: --69689-- Reading syms from /usr/lib/x86_64-linux-gnu/libcurl.so.4.6.0 --69689-- object doesn't have a symbol table So something is definitely wrong here. James Read > > James Read >
------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.html
