|
From: Darrell M.
|
Running valgrind 3.4.1 on ppc I find the following when running a basic test: # ./valgrind ls ==1462== Memcheck, a memory error detector. ==1462== Copyright (C) 2002-2008, and GNU GPL'd, by Julian Seward et al. ==1462== Using LibVEX rev 1884, a library for dynamic binary translation. ==1462== Copyright (C) 2004-2008, and GNU GPL'd, by OpenWorks LLP. ==1462== Using valgrind-3.4.1, a dynamic binary instrumentation framework. ==1462== Copyright (C) 2000-2008, and GNU GPL'd, by Julian Seward et al. ==1462== For more details, rerun with: -v ==1462== valgrind: m_transtab.c:808 (invalidate_icache): Assertion 'cls == 32 || cls == 64 || cls == 128' failed. ==1462== at 0x3802C450: report_and_quit (m_libcassert.c:140) ==1462== by 0x3802C69B: vgPlain_assert_fail (m_libcassert.c:205) ==1462== by 0x38049307: invalidate_icache (m_transtab.c:827) ==1462== by 0x3804960B: vgPlain_add_to_transtab (m_transtab.c:921) ==1462== by 0x38047BBB: vgPlain_translate (m_translate.c:1541) ==1462== by 0x3805706B: handle_tt_miss (scheduler.c:796) ==1462== by 0x38057643: vgPlain_scheduler (scheduler.c:1009) ==1462== by 0x3805AF53: thread_wrapper (syswrap-linux.c:89) ==1462== by 0x3805B0EB: run_a_thread_NORETURN (syswrap-linux.c:122) sched status: running_tid=1 Thread 1: status = VgTs_Runnable ==1462== at 0x400F6C4: (within /lib/ld-2.3.2.so) I see in the code where this is being done but do not understand how it gets set or how to resolve this issue. Any ideas? |