Re: Possible memleak with CRLs / Problems with yacc after 'git clone'

[Nikos Mavrogiannopoulos]

On Sun, 2014-11-30 at 19:42 +0100, Tim Rühsen wrote:
> Hi,
> 
> I tried to look at a memleak reported by valgrind (was a Wget test loading a 
> CRL via
>  gnutls_certificate_set_x509_crl_file()).
> 
> I wondered why valgrind did not give me the line numbers though I installed
>       libgnutls28-dbg:amd64             3.3.8-5
> (on Debian unstable). I am used to get function names and line numbers with a 
> debug library
> installed. (But that is a problem of the Debian packaging.)
> 
> ==11457== 32 bytes in 2 blocks are definitely lost in loss record 19 of 90
> ==11457==    at 0x4C2AD10: calloc (vg_replace_malloc.c:623)
> ==11457==    by 0x55451DA: gnutls_x509_crl_iter_crt_serial (in 
> /usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28.41.0)
> ==11457==    by 0x55687A8: _gnutls_x509_crt_check_revocation (in 
> /usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28.41.0)
> ==11457==    by 0x556F2BE: gnutls_x509_trust_list_verify_crt2 (in 
> /usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28.41.0)
> ==11457==    by 0x55241FE: _gnutls_x509_cert_verify_peers (in 
> /usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28.41.0)
> ==11457==    by 0x4332CD: ssl_check_certificate (gnutls.c:646)
> ==11457==    by 0x419B85: gethttp (http.c:2105)
> ==11457==    by 0x41E1E4: http_loop (http.c:3236)
> ==11457==    by 0x42877B: retrieve_url (retr.c:802)
> ==11457==    by 0x40623E: main (main.c:1688)

Thanks, it seems I managed to figure the issue.

> Compiling stopped with a message about missing yacc (what yacc are you 
> referring to ?).
> I installed byacc and

This is gnulib source, and may require bison (at least this is the yacc
I use).

regards,
Nikos