> Is there any information on adding support for unsupported instructions?
At this point, with >99% of instructions already recognized,
then you should reason by analogy. Use a debugger such as gdb
to trace the execution under valgrind of a similar instruction,
then modify and extend to handle the unimplemented instruction.
For a 'rotate' instruction, use the corresponding right-shift.
Hints:
Assemble the two-line program
_start: .globl _start
.word <the-bits-for-your-instruction>
using
gcc -nostartfiles -nodefaultlibs -nostdlib foo.S
to get an executable file with a .text that has 4==.p_memsz.
Then run memcheck on that executable.
Run "valgrind --help-debug" and look carefully at "Vex options
for all Valgrind tools", particularly --trace-flags.
Read "Debugging Valgrind with GDB" in README_DEVELOPERS.
The code is in VEX/priv/guest_arm*
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
