|
From: Ed S. <ES...@fe...> - 2010-06-07 15:36:00
|
Thank you both for your assistance. > >> It will help a lot if you specify the byte values (say, 8 of them) >> in the instruction stream at address 0x9ceb615. > > Yes. You didn't show the actual bytes it is complaining about, which > are present in the failure message. Without those it is impossible to > say anything. How would I do this? I am new to Linux. The address 0x9ceb615 apparently is the address that the shared library is loaded. How would I get the opcode bytes? > >>> ==1460== by 0x726C4D: clone (in /lib/libc-2.5.so) >>> Red Hat Enterprise Linux 5.2 32-bit >> >> Remember to specify the version of valgrind when you file the bug report. >> The software that you did specify is somewhat old. The current version >> of valgrind is 3.5.0. I am using 3.5.0. > > Try also with --smc-check=all, just in the (unlikely but possible case) > that the library is generating code on the fly. I am trying this. I am still reading through the log file trying to see if it changed anything. Thanks for your help, -Ed |