From 488110f800897e3a71054e1e821746acc71c3333 Mon Sep 17 00:00:00 2001
From: Eugene Syromyatnikov <evgsyr@gmail.com>
Date: Thu, 18 Jan 2018 13:16:35 +0100
Subject: [PATCH] strace.1.in: clarify mpers flags in strace -V output

The previous description was a bit dated.

* strace.1.in (.SH "MULTIPLE PERSONALITY SUPPORT"): Remove "no-m32" and
"no-mx32", describe the situation when some of mpers flags are not
present in strace -V output.
---
 strace.1.in | 25 +++++++++++++------------
 1 file changed, 13 insertions(+), 12 deletions(-)

diff --git a/strace.1.in b/strace.1.in
index 94d0a2e7..645eabb8 100644
--- a/strace.1.in
+++ b/strace.1.in
@@ -899,10 +899,6 @@ can trace and properly decode non-native 32-bit binaries.
 .B strace
 can trace, but cannot properly decode non-native 32-bit binaries.
 .TP
-.B no-m32
-.B strace
-cannot trace non-native 32-bit binaries.
-.TP
 .B mx32-mpers
 .B strace
 can trace and properly decode non-native 32-on-64-bit binaries.
@@ -910,15 +906,20 @@ can trace and properly decode non-native 32-on-64-bit binaries.
 .B no-mx32-mpers
 .B strace
 can trace, but cannot properly decode non-native 32-on-64-bit binaries.
-.TP
-.B no-mx32
-.B strace
-cannot trace non-native 32-on-64-bit binaries.
 .PP
-Note that these flags refer only to the binaries in the non-native ABI;
-.B strace
-is expected to be able to trace and properly decode applications that use its
-native ABI.
+If the output contains neither
+.B m32-mpers
+nor
+.BR no-m32-mpers ,
+then decoding of non-native 32-bit binaries is not implemented at all
+or not applicable.
+.PP
+Likewise, if the output contains neither
+.B mx32-mpers
+nor
+.BR no-mx32-mpers ,
+then decoding of non-native 32-on-64-bit binaries is not implemented at all
+or not applicable.
 .SH NOTES
 It is a pity that so much tracing clutter is produced by systems
 employing shared libraries.
-- 
2.40.0