Document -k option as experimental

strace -k does not produce a reliable output on all supported
configurations yet, even basic strace-k.test is known to fail
on some of them.

* strace.c (usage): Document -k option as experimental.
* strace.1: Likewise.
* NEWS: Likewise.

3 files changed, 3 insertions, 3 deletions

diff --git a/NEWS b/NEWS
index 3347236d..a311c34d 100644
--- a/NEWS
+++ b/NEWS
@@ -6,7 +6,7 @@ Noteworthy changes in release 4.9 (????-??-??)
     added --enable-arm-oabi option to enable it at configure time.
 
 * Improvements
-  * Added -k option to print stack trace after each traced syscall.
+  * Added experimental -k option to print stack trace after each traced syscall.
   * Added -w option to produce stats on syscall latency.
     (addresses Debian bug #457497).
   * Added ARC architecture support.
diff --git a/strace.1 b/strace.1
index c310d65a..2a24c383 100644
--- a/strace.1
+++ b/strace.1
@@ -268,7 +268,7 @@ Print the help summary.
 Print the instruction pointer at the time of the system call.
 .TP
 .B \-k
-Print the execution stack trace of the traced processes after each system call.
+Print the execution stack trace of the traced processes after each system call (experimental).
 .TP
 .B \-q
 Suppress messages about attaching, detaching etc.  This happens
diff --git a/strace.c b/strace.c
index 46c9d63e..4154cde6 100644
--- a/strace.c
+++ b/strace.c
@@ -238,7 +238,7 @@ usage: strace [-CdffhiqrtttTvVxxy] [-I n] [-e expr]...\n\
 -P path -- trace accesses to path\n\
 "
 #ifdef USE_LIBUNWIND
-"-k obtain stack trace between each syscall\n\
+"-k obtain stack trace between each syscall (experimental)\n\
 "
 #endif
 /* ancient, no one should use it