|
From: Konstantin S. <kon...@gm...> - 2009-02-06 07:31:15
|
Hi Valgrind developers, I've seen the recent checkins related to stack unwinding. Are they expected to fix all known issues with stack traces on x86_64? This is what I see with the fresh trunk: ==27019== ==27019== Use of uninitialised value of size 8 ==27019== at 0xBD3214F: something_meaningful ==27019== by 0x7A2C730C750BD1E8: ??? ==27019== by 0xD075D9E9E5D0101: ??? ==27019== by 0x4EAF8BD8815341D7: ??? ==27019== by 0x262956DDE630E67F: ??? ==27019== by 0xEBD8C81E497E5F10: ??? ==27019== by 0x6C6DCB5AF54DD8FF: ??? ==27019== by 0xBF7C9DAE3F6B4DF1: ??? ==27019== by 0x7094A51C580E33E: ??? ==27019== by 0x691AAF338D45C9C8: ??? ==27019== by 0x96D13F92611B33C5: ??? ==27019== by 0x1A2633D708F8FA01: ??? ==27019== ==27019== Use of uninitialised value of size 8 ==27019== at 0xBD3214F: something_meaningful ==27019== by 0x7A2C730C750BD1E8: ??? ==27019== by 0xD075D9E9E5D0101: ??? ==27019== by 0xF: ??? ==27019== by 0xF: ??? ==27019== by 0xF: ??? ==27019== by 0xF: ??? ==27019== by 0xF: ??? ==27019== by 0xF: ??? ==27019== by 0xF: ??? ==27019== by 0xF: ??? ==27019== by 0xF: ??? Is there anything I can provide you to help debug this? Thanks, --kcc |