Ah, it looks like _start the the real program entry point, assigned in valt_load_address_arm_linux.lds (probably).
Like any other assembler symbol, the entry point needs to be properly tagged as a function symbol in order for the process to start executing in Thumb. Currently, it looks like the code at _start is being interpreted as ARM code, causing a SIGILL. $ gdb ./valgrind [...] Reading symbols from /home/ubuntu/src/review/valgrind/valgrind-3.6.0~svn20100212/tmp-prefix/usr/bin/valgrind...done. (gdb) r Starting program: /home/ubuntu/src/review/valgrind/valgrind-3.6.0~svn20100212/tmp-prefix/usr/bin/valgrind Executing new program: /usr/lib/valgrind/memcheck-arm-linux valgrind: no program specified valgrind: Use --help for more information. Program exited with code 01. (gdb) q ** Patch added: "modified patch which adds the proper tagging so that the entry point symbol _start is recognised as a thumb function symbol" http://launchpadlibrarian.net/41123816/valgrind__start_arm_literal_fix-3.diff -- 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
