|
From: Tyler N. <tyl...@co...> - 2003-11-18 00:48:24
|
Trying to get valgrind to work on a new system. I am getting this as the output for ls (and several other programs) ==20208== Command line: ==20208== ls ==20208== Startup, with flags: ==20208== --suppressions=/usr/lib/valgrind/default.supp ==20208== -v ==20208== Reading syms from /bin/ls ==20208== object doesn't have a symbol table ==20208== object doesn't have any debug info ==20208== Reading syms from /lib/ld-2.3.2.so ==20208== object doesn't have any debug info ==20208== Reading syms from /usr/lib/valgrind/vgskin_memcheck.so ==20208== object doesn't have any debug info ==20208== Reading syms from /usr/lib/valgrind/valgrind.so ==20208== object doesn't have any debug info ==20208== Reading syms from /usr/lib/valgrind/libpthread.so ==20208== object doesn't have any debug info ==20208== Reading syms from /lib/librt-2.3.2.so ==20208== object doesn't have any debug info ==20208== Reading syms from /lib/libc-2.3.2.so ==20208== object doesn't have any debug info ==20208== Reading suppressions file: /usr/lib/valgrind/default.supp ==20208== Estimated CPU clock rate is 2121 MHz ==20208== REPLACING libc(__GI___errno_location) with libpthread(__errno_location) ==20208== REPLACING libc(__GI___h_errno_location) with libpthread(__h_errno_location) ==20208== REPLACING libc(__GI___res_state) with libpthread(__res_state) ==20208== ==20208== TRANSLATE: 0x402A1980 redirected to 0x4023B13A disInstr: unhandled instruction bytes: 0xF 0xD 0x8A 0x80 Illegal instruction I'm not to good at this, but I think it's the prefetchw command. Any idea how difficult this is to implement? Tyler Nielsen |