Thanks, it all makes sense now! I was also misreading the ARM/Thumb instructions reference card
Sadly, the patch causes valgrind to FTBFS as follows: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../VEX/pub -DVGA_arm=1 -DVGO_linux=1 -DVGP_arm_linux=1 -I../coregrind -DVG_LIBDIR="\"/home/ubuntu/valgrind/valgrind-3.6.0~svn20100212/prefix/lib/valgrind"\" -DVG_PLATFORM="\"arm-linux\"" -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -Wno-long-long -fno-stack-protector -Wno-pointer-sign -fno-stack-protector -MT libcoregrind_arm_linux_a-m_main.o -MD -MP -MF .deps/libcoregrind_arm_linux_a-m_main.Tpo -c -o libcoregrind_arm_linux_a-m_main.o `test -f 'm_main.c' || echo './'`m_main.c /tmp/ccNzAyWv.s: Assembler messages: /tmp/ccNzAyWv.s:29: Error: offset out of range /tmp/ccNzAyWv.s:30: Error: offset out of range /tmp/ccNzAyWv.s:32: Error: offset out of range make[3]: *** [libcoregrind_arm_linux_a-m_main.o] Error 1 make[3]: Leaving directory `/home/ubuntu/valgrind/valgrind-3.6.0~svn20100212/coregrind' -- Foobared on armel https://bugs.launchpad.net/bugs/537458 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
