[Valgrind-users] Problem with valgrind-ppc on QEMU

[Lionel U. <lio...@fr...>]

Hi all,

To test some stuff I wanted to run valgrind-ppc on a QEMU image running on
my X86 box (it will be really slow, but well, it's just to do some 'proof of
concept' stuff).

Anyway, I had first the issue that I was not able to build the Valgrind
(3.1.1) version out of the box due to the fact that 'as' was barfing on the
Altivec test (in m_machine.c) because QEMU only emulates a G3 (/proc/cpuinfo
tells '604' as CPU).

After forcing it to FALSE I was able to build Valgrind (on the box itself -
an emulated Debian Sarge).

The problem is that when I start valgrind, I get this:

debian-ppc32:~# valgrind /bin/ls
==584== Memcheck, a memory error detector.
==584== Copyright (C) 2002-2005, and GNU GPL'd, by Julian Seward et al.
==584== Using LibVEX rev 1575, a library for dynamic binary translation.
==584== Copyright (C) 2004-2005, and GNU GPL'd, by OpenWorks LLP.
==584== Using valgrind-3.1.1, a dynamic binary instrumentation framework.
==584== Copyright (C) 2000-2005, and GNU GPL'd, by Julian Seward et al.
==584== For more details, rerun with: -v
==584== 
==584== 
==584== Process terminating with default action of signal 4 (SIGILL)
==584==  Illegal opcode at address 0x7005F36C
==584==    at 0x400F6C4: (within /lib/ld-2.3.2.so)
==584== 
==584== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==584== malloc/free: in use at exit: 0 bytes in 0 blocks.
==584== malloc/free: 0 allocs, 0 frees, 0 bytes allocated.
==584== For counts of detected errors, rerun with: -v
==584== All heap blocks were freed -- no leaks are possible.
Illegal instruction

So now I have a dilemna: where is the bug - in QEMU or in Valgrind :-) ?
Does anyone know how I could progress further on this ?

          Lionel

-- 
		 Lionel Ulmer - http://www.bbrox.org/