|
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 |
|
From: Jeremy F. <je...@go...> - 2003-11-18 01:05:20
|
On Mon, 2003-11-17 at 16:48, Tyler Nielsen wrote: > 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? prefetchw - that's an AMD 3dnow! instruction right? I think it's a bug in your distro if it's using 3dnow instructions on a CPU which doesn't claim to support them (unless, of course, we are claiming to do so accidentally). What's your CPU? J |
|
From: Tyler N. <tyl...@co...> - 2003-11-18 02:38:31
|
On Mon, 2003-11-17 at 18:05, Jeremy Fitzhardinge wrote: > On Mon, 2003-11-17 at 16:48, Tyler Nielsen wrote: > > 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? > > prefetchw - that's an AMD 3dnow! instruction right? I think it's a bug > in your distro if it's using 3dnow instructions on a CPU which doesn't > claim to support them (unless, of course, we are claiming to do so > accidentally). What's your CPU? > > J > I think my CPU supports them. I have an AMD Athlon XP 2600+. I just figured valgrind doesn't know what to do with the command. cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 8 model name : AMD Athlon(TM) XP 2600+ stepping : 1 cpu MHz : 2083.203 cache size : 256 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow bogomips : 4104.19 Tyler |
|
From: Nicholas N. <nj...@ca...> - 2003-11-18 08:42:29
|
On Mon, 17 Nov 2003, Tyler Nielsen wrote: > > prefetchw - that's an AMD 3dnow! instruction right? I think it's a bug > > in your distro if it's using 3dnow instructions on a CPU which doesn't > > claim to support them (unless, of course, we are claiming to do so > > accidentally). What's your CPU? > > > I think my CPU supports them. I have an AMD Athlon XP 2600+. I just > figured valgrind doesn't know what to do with the command. Yes. Valgrind doesn't support any 3dNow! instructions, because they're not used very much. I don't think Valgrind does any kind of checking for 3dNow! support. It would be quite easy to add support for prefetchw to coregrind/vg_to_ucode.c, since you can just ignore the instruction and not generate any UCode for it. That won't help you much if your program uses other 3dNow! instructions. Can you remove them from your program, eg. by compiling with different options? N |
|
From: Tyler N. <tyl...@co...> - 2003-11-18 20:23:43
|
On Tue, 2003-11-18 at 01:42, Nicholas Nethercote wrote: > On Mon, 17 Nov 2003, Tyler Nielsen wrote: > > It would be quite easy to add support for prefetchw to > coregrind/vg_to_ucode.c, since you can just ignore the instruction and not > generate any UCode for it. That won't help you much if your program uses > other 3dNow! instructions. Can you remove them from your program, eg. by > compiling with different options? > Thanks for the help, I'll try to remove the 3dNow instructions. Tyler |