|
From: Konstantin S. <kon...@gm...> - 2009-02-06 11:11:57
|
> svn co svn://svn.valgrind.org/valgrind/branches/VALGRIND_3_4_BRANCH branch34 > > See if it still has the problem. Same thing. > > Secondly, do the usual two things: > > 1. See if you can make a small test case that shows it. Without that > it will be close to impossible to fix. > That's a challenge. :) Right now I have only one reproducer somewhere inside the openssl's assembly file: ==11896== Use of uninitialised value of size 8 ==11896== at 0xC32B140: bn_mul_mont (x86_64-mont.s:151) ==11896== by 0xEFD8ADCFE9793F71: ??? ==11896== by 0x4DC04AA2FB5DAAB0: ??? ==11896== by 0xB18F5B34F8340518: ??? ==11896== by 0x9629706EA81DAD54: ??? ... Maybe this file (ftp://ftp.free.fr/.mirrors1/ftp.netbsd.org/NetBSD-current/src/crypto/dist/openssl/crypto/bn/asm/x86_64-mont.pl) has some valgrind-unfriendly stuff? Will see if I can get something simpler... --kcc > 2. If (1) does not work, do a binary search on the svn versions to find > the commit number that caused the problem. > > J > |