Alessandro Ghedini <gh...@debian.org> writes: > AFAICT building/running valgrind on ARMv5 is not supported (also see #592614) > but there are a couple of patches floating around [0] to add support for them. > I don't know if they actually work (or if they apply at all) though.
ok. I don't expect you to fix upstream code :) However, since valgrind is a shell script maybe it could inform the user about this? Something like this: if grep -q "^CPU architecture: 4" /proc/cpuinfo || grep -q "^CPU architecture: 5" /proc/cpuinfo; then echo "valgrind does not yet support ARMv4 or ARMv5" exit 1 fi Example cpuinfo from openmoko: Processor : ARM920T rev 0 (v4l) BogoMIPS : 199.47 Features : swp half thumb CPU implementer : 0x41 CPU architecture: 4T CPU variant : 0x1 CPU part : 0x920 CPU revision : 0 Hardware : GTA02 Revision : 0360 Serial : 0000000000000000 Example cpuinfo from the marvell development board: Processor : Feroceon rev 0 (v5l) BogoMIPS : 999.42 Features : swp half thumb fastmult vfp edsp CPU implementer : 0x41 CPU architecture: 5TE CPU variant : 0x1 CPU part : 0x926 CPU revision : 0 Hardware : Marvell DB-78x00-BP Development Board Revision : 0000 Serial : 0000000000000000 Example cpuinfo from marvell sheevaplug: Processor : Feroceon 88FR131 rev 1 (v5l) BogoMIPS : 1192.75 Features : swp half thumb fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant : 0x2 CPU part : 0x131 CPU revision : 1 Hardware : Marvell eSATA SheevaPlug Reference Board Revision : 0000 Serial : 0000000000000000 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
