ltrace complains about unexpected instruction

[Vincent Stehlé]

Binary package hint: ltrace

On an ARM Cortex-A9, ltrace complains about unexpected instruction.
For example:

$ ltrace ls
...
fclose(0x402785d8 <unfinished ...>
unexpected instruction 0xdf004667 at 0x40196892
unexpected instruction 0xdf004667 at 0x40196892
SYS_munmap(0x4006e000, 4096) = 0
<... fclose resumed> ) = 0
__fpending(0x40278678, 0, 0x40278538, 135880, 0) = 0
fclose(0x40278678 <unfinished ...>
unexpected instruction 0xdf004667 at 0x40196892
unexpected instruction 0xdf004667 at 0x40196892
<... fclose resumed> ) = 0
unexpected instruction 0xdf004667 at 0x40196892
+++ exited (status 0) +++

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: ltrace 0.5.3-2ubuntu5
ProcVersionSignature: Ubuntu 2.6.35-ti903.8+ti+release2-omap4 2.6.35.3
Uname: Linux 2.6.35-ti903-omap4 armv7l
Architecture: armel
Date: Tue Sep 14 06:21:08 2010
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ltrace

[Vincent Stehlé (vstehle)]

Looking at the ARMv7a spec, the two instructions 0xdf004667 look like the following two 16b thumb instructions:

0xdf00 SVC #0
0x4667 MOV R7, R12

[Zach Welch (zwelch)]

The attached patch makes ltrace understand syscalls made in Thumb-2 mode.

[Launchpad Janitor (janitor)]

This bug was fixed in the package ltrace - 0.5.3-2ubuntu6

---------------
ltrace (0.5.3-2ubuntu6) maverick; urgency=low

  * Fix ARM syscall_p to handle Thumb-2 mode (Zach Welch). LP: #639796.
 -- Matthias Klose <email address hidden> Fri, 01 Oct 2010 16:06:14 +0200