---

   strace    ( 1 )

---

MULTIPLE PERSONALITIES SUPPORT

On some architectures, strace supports decoding of syscalls for processes that use different ABI rather than the one strace uses. Specifically, in addition to decoding native ABI, strace can decode the following ABIs on the following architectures:

┌───────────────────┬─────────────────────────┐ │Architecture │ ABIs supported │ ├───────────────────┼─────────────────────────┤ │x86_64 │ i386, x32 [1]; i386 [2] │ ├───────────────────┼─────────────────────────┤ │AArch64 │ ARM 32-bit EABI │ ├───────────────────┼─────────────────────────┤ │PowerPC 64-bit [3] │ PowerPC 32-bit │ ├───────────────────┼─────────────────────────┤ │s390x │ s390 │ ├───────────────────┼─────────────────────────┤ │SPARC 64-bit │ SPARC 32-bit │ ├───────────────────┼─────────────────────────┤ │TILE 64-bit │ TILE 32-bit │ └───────────────────┴─────────────────────────┘ [1] When strace is built as an x86_64 application [2] When strace is built as an x32 application [3] Big endian only

This support is optional and relies on ability to generate and parse structure definitions during the build time. Please refer to the output of the strace -V command in order to figure out what support is available in your strace build ("non-native" refers to an ABI that differs from the ABI strace has):

m32-mpers strace can trace and properly decode non-native 32-bit binaries. no-m32-mpers strace can trace, but cannot properly decode non-native 32-bit binaries. mx32-mpers strace can trace and properly decode non-native 32-on-64-bit binaries. no-mx32-mpers strace can trace, but cannot properly decode non-native 32-on-64-bit binaries.

If the output contains neither m32-mpers nor no-m32-mpers, then decoding of non-native 32-bit binaries is not implemented at all or not applicable.

Likewise, if the output contains neither mx32-mpers nor no- mx32-mpers, then decoding of non-native 32-on-64-bit binaries is not implemented at all or not applicable.