> * Apply #2.
> * Apply #3 in VEX.
> * Revert coregrind/m_dispatch/dispatch-arm-linux.S.
> * Apply #6.
>
> Is this how you've meant it?
Yes.
> I've tried this on r12305 and was able to build it for arm-linux-gnu.
> Running it on PXA255 under Debian results in an illegal instruction at
> 0x38041f64, which seems to be the following:
>
> 38041f50 <do_syscall_WRK>:
> 38041f50: e92d00b0 stmdb sp!, {r4, r5, r7}
> 38041f54: e59d400c ldr r4, [sp, #12]
> 38041f58: e59d5010 ldr r5, [sp, #16]
> 38041f5c: e59d7014 ldr r7, [sp, #20]
> 38041f60: ef000000 svc 0x00000000
> 38041f64: e8bd00b0 ldmia sp!, {r4, r5, r7}
> 38041f68: e12fff1e bx lr
What is PXA255 [give URL etc.], and which version of Debian, and which hardware?
The opcode 'svc' is a system call, and 0x38041f64 is the immediately
following address, so the SIGILL is a complaint from the syscall.
There are 6 arguments (r0,r1,r2,r3,r4,r5} and the syscall number
was in r7. Find syscall number and argument values, such as by using gdb.
Or perhaps the last few lines of
valgrind --trace-syscalls=yes ./my_app ...
can give some clues.
--
------------------------------------------------------------------------------
Systems Optimization Self Assessment
Improve efficiency and utilization of IT resources. Drive out cost and
improve service delivery. Take 5 minutes to use this Systems Optimization
Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
