Hi list,
I cross-compile valgrind-3.6.0 to run on devkit8000 board (armv7)...
when I run "valgrind --tool=cachegrind ls", this error happens:


==702== Cachegrind, a cache and branch-prediction profiler
==702== Copyright (C) 2002-2010, and GNU GPL'd, by Nicholas Nethercote et al.
==702== Using Valgrind-3.6.0 and LibVEX; rerun with -h for copyright info
==702== Command: ls
==702==
--702-- Warning: Cannot auto-detect cache config on ARM, using one or
more defaults
disInstr(arm): unhandled instruction: 0xF421070D
                 cond=15(0xF) 27:20=66(0x42) 4:4=0 3:0=13(0xD)
==702== valgrind: Unrecognised instruction at address 0x401721c.
==702== Your program just tried to execute an instruction that Valgrind
==702== did not recognise.  There are two possible reasons for this.
==702== 1. Your program has a bug and erroneously jumped to a non-code
==702==    location.  If you are running Memcheck and you just saw a
==702==    warning about a bad jump, it's probably your program's fault.
==702== 2. The instruction is legitimate but Valgrind doesn't handle it,
==702==    i.e. it's Valgrind's fault.  If you think this is the case or
==702==    you are not sure, please let us know and we'll try to fix it.
==702== Either way, Valgrind will now raise a SIGILL signal which will
==702== probably kill your program.
==702==
==702== Process terminating with default action of signal 4 (SIGILL)
==702==  Illegal opcode at address 0x401721C
==702==    at 0x401721C: memcpy (in /lib/ld-2.9.so)
...
Illegal instruction

Do you know what is the problem?
Thanks,
Nuno Cardoso.

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to