|
From: Tom H. <to...@co...> - 2009-02-06 11:27:42
|
Konstantin Serebryany wrote: > 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: ??? > ... That's a hand crafted assembler routine, so unless the author has either taken the trouble to setup a traditional x86 stack frame by pushing the frame pointer, or has added DWARF declarations to describe how to unwind the stack, then valgrind won't be able to unwind out of it. Can gdb unwind out of that function if you set a break point inside it? Tom -- Tom Hughes (to...@co...) http://www.compton.nu/ |