Re: some binaries crash with SIGILL on Zybo-Z7-20

[Nick Hudson <nick.hudson%gmx.co.uk@localhost>]

On 31/10/2018 10:37, Alexander Nasonov wrote:
> Martin Husemann wrote:
> > Not sure what that tool does, but this is how objdump -D looks on my armv5
> > machine:
>
> You're right. I see the same instruction if I pass -D
>
> # objdump -D /usr/lib/libc.so.12.211 | sed -e '/_string_hash_func>/,/^$/!d'
> 000a03e4 <_string_hash_func>:
>   
> ...
>
>    a0580:       e103409e        swp     r4, lr, [r3]
>    a0584:       ea000001        b       a0590 <_string_hash_func+0x1ac>
>    a0588:       e3550000        cmp     r5, #0
>    a058c:       1afffffb        bne     a0580 <_string_hash_func+0x19c>
>    a0590:       e3540000        cmp     r4, #0
>    a0594:       1afffff9        bne     a0580 <_string_hash_func+0x19c>
>    

You should really run a evbarm-earmv7hf userland on Zybo. You've got a 
swp because evbarm defaults to armv5 and

https://nxr.netbsd.org/xref/src/sys/arch/arm/include/lock.h#76

It's very likely your chip doesn't support swp{,b}

hw.machdep.id_isar[3:0] is zero if they aren't

Nick