|
From: John R. <jr...@bi...> - 2010-06-07 14:44:59
|
> Question: Is there a way to Valgrind to stay out of a shared library? No. Any instruction which accesses data memory must be examined. > ==1460== valgrind: Unrecognised instruction at address 0x9ceb615. http://valgrind.org/docs/manual/faq.html#faq.msgdeath It will help a lot if you specify the byte values (say, 8 of them) in the instruction stream at address 0x9ceb615. > ==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. -- |