That's a bit strange, considering that it does work well on the A8. There must be something a bit funny about your setup. I wonder if it is to do with ucLibc. Or something alignment related, maybe.
w.r.t. your SoC, what capabilities does the CPU have? Neon? VFP? > ==483== Process terminating with default action of signal 4 (SIGILL) > ==483== Illegal opcode at address 0x380AC1A8 > ==483== at 0x4000960: _start (in /lib/ld-uClibc-0.9.30.2.so) It would be useful to know what instruction is at 0x380AC1A8. I can't guess whether that is part of the main valgrind executable or whether it is code generated by valgrind's JIT. Can you objdump -d of memcheck-arm-linux and see if you can find that address? If not, you'll have to be a remote debug server :-) Try running with the flags --trace-flags=10001110 --trace-notbelow=0. This will generate a huge amount of output, but it should make it possible to make some sense of what's going on at 0x380AC1A8 and/or 0x4000960. Bear in mind you can't post more than 40k of message to the list, so you may have to do some pruning. J ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
