Running "make check" under valgrind
|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
 |
Running "make check" under valgrind
by Bugzilla from bradh@frogmouth.net
::
Rate this Message:
Hi,
When I run "make check" with valgrind support, I'm seeing about 20 tests that are showing valgrind errors. Looks like a common backtrace: ==28786== Conditional jump or move depends on uninitialised value(s) ==28786== at 0x4130789: _gcry_mpi_print (mpicoder.c:583) ==28786== by 0x40E4A48: gcry_mpi_print (visibility.c:308) ==28786== by 0x40474B8: wrap_gcry_mpi_print (mpi-libgcrypt.c:76) ==28786== by 0x4044109: _gnutls_dh_common_print_server_kx (auth_dh_common.c:326) ==28786== by 0x404F3F3: gen_psk_server_kx (auth_dhe_psk.c:157) ==28786== by 0x4027C57: _gnutls_send_server_kx_message (gnutls_kx.c:200) ==28786== by 0x40245D7: _gnutls_handshake_server (gnutls_handshake.c:2762) ==28786== by 0x4024C89: gnutls_handshake (gnutls_handshake.c:2435) ==28786== by 0x8049717: doit (dhepskself.c:272) ==28786== by 0x80499EC: main (utils.c:148) ==28786== ==28786== Conditional jump or move depends on uninitialised value(s) ==28786== at 0x4130789: _gcry_mpi_print (mpicoder.c:583) ==28786== by 0x40E4A48: gcry_mpi_print (visibility.c:308) ==28786== by 0x40474B8: wrap_gcry_mpi_print (mpi-libgcrypt.c:76) ==28786== by 0x404412C: _gnutls_dh_common_print_server_kx (auth_dh_common.c:327) ==28786== by 0x404F3F3: gen_psk_server_kx (auth_dhe_psk.c:157) ==28786== by 0x4027C57: _gnutls_send_server_kx_message (gnutls_kx.c:200) ==28786== by 0x40245D7: _gnutls_handshake_server (gnutls_handshake.c:2762) ==28786== by 0x4024C89: gnutls_handshake (gnutls_handshake.c:2435) ==28786== by 0x8049717: doit (dhepskself.c:272) ==28786== by 0x80499EC: main (utils.c:148) ==28786== ==28786== Conditional jump or move depends on uninitialised value(s) ==28786== at 0x4130789: _gcry_mpi_print (mpicoder.c:583) ==28786== by 0x40E4A48: gcry_mpi_print (visibility.c:308) ==28786== by 0x40474B8: wrap_gcry_mpi_print (mpi-libgcrypt.c:76) ==28786== by 0x404414F: _gnutls_dh_common_print_server_kx (auth_dh_common.c:328) ==28786== by 0x404F3F3: gen_psk_server_kx (auth_dhe_psk.c:157) ==28786== by 0x4027C57: _gnutls_send_server_kx_message (gnutls_kx.c:200) ==28786== by 0x40245D7: _gnutls_handshake_server (gnutls_handshake.c:2762) ==28786== by 0x4024C89: gnutls_handshake (gnutls_handshake.c:2435) ==28786== by 0x8049717: doit (dhepskself.c:272) ==28786== by 0x80499EC: main (utils.c:148) ==28787== Conditional jump or move depends on uninitialised value(s) ==28787== at 0x4130789: _gcry_mpi_print (mpicoder.c:583) ==28787== by 0x40E4A48: gcry_mpi_print (visibility.c:308) ==28787== by 0x40474B8: wrap_gcry_mpi_print (mpi-libgcrypt.c:76) ==28787== by 0x40447A6: _gnutls_gen_dh_common_client_kx (auth_dh_common.c:142) ==28787== by 0x404F1D9: gen_psk_client_kx (auth_dhe_psk.c:89) ==28787== by 0x4027A1F: _gnutls_send_client_kx_message (gnutls_kx.c:295) ==28787== by 0x4023F5F: _gnutls_handshake_client (gnutls_handshake.c:2576) ==28787== by 0x4024D07: gnutls_handshake (gnutls_handshake.c:2431) ==28787== by 0x8049304: client (dhepskself.c:93) ==28787== by 0x8049566: doit (dhepskself.c:351) ==28787== by 0x80499EC: main (utils.c:148) Is anyone else seeing this? Brad _______________________________________________ Gnutls-devel mailing list Gnutls-devel@... http://lists.gnu.org/mailman/listinfo/gnutls-devel |
|
|
Re: Running "make check" under valgrind
by Simon Josefsson-2
::
Rate this Message:
Brad Hards <bradh@...> writes:
> Hi, > > When I run "make check" with valgrind support, I'm seeing about 20 tests that > are showing valgrind errors. Looks like a common backtrace: > > ==28786== Conditional jump or move depends on uninitialised value(s) > ==28786== at 0x4130789: _gcry_mpi_print (mpicoder.c:583) ... > Is anyone else seeing this? Nope. Which libgcrypt version are you using? /Simon _______________________________________________ Gnutls-devel mailing list Gnutls-devel@... http://lists.gnu.org/mailman/listinfo/gnutls-devel |
|
|
Re: Running "make check" under valgrind
by Bugzilla from bradh@frogmouth.net
::
Rate this Message:
On Thursday 05 November 2009 23:58:18 you wrote:
> Nope. Which libgcrypt version are you using? As it turned out, it was some svn version that I had installed. However I've removed that, rebuilt everything, and I can repeat that with 1.4.4 packages from my distro (libgcrypt-1.4.4-6.fc11). I also tried a more up-to-date svn version of libgcrypt (At revision 1406.) but no difference. A svn version of libgpg-error also made no difference. Brad _______________________________________________ Gnutls-devel mailing list Gnutls-devel@... http://lists.gnu.org/mailman/listinfo/gnutls-devel |
|
|
Re: Running "make check" under valgrind
by Simon Josefsson-2
::
Rate this Message:
Brad Hards <bradh@...> writes:
> On Thursday 05 November 2009 23:58:18 you wrote: >> Nope. Which libgcrypt version are you using? > As it turned out, it was some svn version that I had installed. However I've > removed that, rebuilt everything, and I can repeat that with 1.4.4 packages > from my distro (libgcrypt-1.4.4-6.fc11). > > I also tried a more up-to-date svn version of libgcrypt (At revision 1406.) > but no difference. A svn version of libgpg-error also made no difference. Strange, I'm using libgcrypt from debian and don't see this. Could you try to debug it further to see if there is a genuine memory leak? Hm, I realized I have a ~/.valgrind: --memcheck:leak-check=full --memcheck:leak-resolution=high --memcheck:show-reachable=yes --memcheck:num-callers=50 --suppressions=/home/jas/src/gnutls/tests/libgcrypt.supp The libgcrypt.supp file in GnuTLS lists some known memory leaks in libgcrypt. However, your leaks doesn't look like any of them, but maybe you could check that file to make sure. /Simon _______________________________________________ Gnutls-devel mailing list Gnutls-devel@... http://lists.gnu.org/mailman/listinfo/gnutls-devel |
| Free embeddable forum powered by Nabble | Forum Help |
