Bug 348536

Summary: Unhandled instructions 0xEE190F1D & 0xEC510F1E
Product: [Developer tools] valgrind Reporter: Daniel <d.ansorregui>
Component: memcheckAssignee: Julian Seward <jseward>
Status: RESOLVED DUPLICATE    
Severity: normal CC: tom
Priority: NOR    
Version: 3.10 SVN   
Target Milestone: ---   
Platform: Android   
OS: Other   
Latest Commit: Version Fixed In:

Description Daniel 2015-06-01 09:36:51 UTC 
WARNING: linker: Unsupported flags DT_FLAGS_1=0x421 disInstr(arm): unhandled instruction: 0xEC510F1E cond=14(0xE) 27:20=197(0xC5) 4:4=1 3:0=14(0xE) ==26688== valgrind: Unrecognised instruction at address 0x5534b48. ==26688== at 0x5534B48: _armv7_tick (in /system/lib/libcrypto.so) ==26688== Your program just tried to execute an instruction that Valgrind ==26688== did not recognise. There are two possible reasons for this. ==26688== 1. Your program has a bug and erroneously jumped to a non-code ==26688== location. If you are running Memcheck and you just saw a ==26688== warning about a bad jump, it's probably your program's fault. ==26688== 2. The instruction is legitimate but Valgrind doesn't handle it, ==26688== i.e. it's Valgrind's fault. If you think this is the case or ==26688== you are not sure, please let us know and we'll try to fix it. ==26688== Either way, Valgrind will now raise a SIGILL signal which will ==26688== probably kill your program. disInstr(arm): unhandled instruction: 0xEE190F1D cond=14(0xE) 27:20=225(0xE1) 4:4=1 3:0=13(0xD)

Reproducible: Always
Comment 1 Daniel 2015-06-01 09:54:52 UTC 
Sry, I did not filled the details properly before.

The bug is always reproducible. Running Valgrind in ARM (S6 device), on the surfaceflinger system service. In 32bit mode. WIth the latests version 3.10.1

The errors are:
disInstr(arm): unhandled instruction: 0xEC510F1E cond=14(0xE) 27:20=197(0xC5) 4:4=1 3:0=14(0xE)
disInstr(arm): unhandled instruction: 0xEE190F1D cond=14(0xE) 27:20=225(0xE1) 4:4=1 3:0=13(0xD)

Located at: 
_armv7_tick (in /system/lib/libcrypto.so)
_fips_armv7_tick (in /system/lib/libcrypto.so)

I added a comment to another bugreport, but it is not exactly the same error, so I am adding a proper new bug report here.
Comment 2 Tom Hughes 2015-06-01 13:05:52 UTC 
These are already covered by BZ#331178 (for 0xEE190F1D) and BZ#344802 (for 0xEC510F1E).

*** This bug has been marked as a duplicate of bug 331178 ***
Comment 3 Julian Seward 2015-08-17 11:26:45 UTC 
0xEE190F1D = mrc	15, 0, r0, cr9, cr13, {0}
0xEC510F1E = mrrc	15, 1, r0, r1, cr14