summaryrefslogtreecommitdiff
path: root/debian/patches/0006-doc-explain-the-floating-point-flag-in-kdb-output.patch
diff options
context:
space:
mode:
Diffstat (limited to 'debian/patches/0006-doc-explain-the-floating-point-flag-in-kdb-output.patch')
-rw-r--r--debian/patches/0006-doc-explain-the-floating-point-flag-in-kdb-output.patch30
1 files changed, 30 insertions, 0 deletions
diff --git a/debian/patches/0006-doc-explain-the-floating-point-flag-in-kdb-output.patch b/debian/patches/0006-doc-explain-the-floating-point-flag-in-kdb-output.patch
new file mode 100644
index 0000000..f2cfe1d
--- /dev/null
+++ b/debian/patches/0006-doc-explain-the-floating-point-flag-in-kdb-output.patch
@@ -0,0 +1,30 @@
+From ce7a47ac13e16c8f0ce667c33a5946b5e2d95b23 Mon Sep 17 00:00:00 2001
+From: Justus Winter <4winter@informatik.uni-hamburg.de>
+Date: Mon, 9 Jun 2014 18:33:30 +0200
+Subject: [PATCH 6/6] doc: explain the floating point flag in kdb output
+
+* doc/mach.texi (Kernel Debugger Commands): Explain the floating point
+flag.
+---
+ doc/mach.texi | 5 +++--
+ 1 file changed, 3 insertions(+), 2 deletions(-)
+
+diff --git a/doc/mach.texi b/doc/mach.texi
+index 49c0d67..2da670f 100644
+--- a/doc/mach.texi
++++ b/doc/mach.texi
+@@ -7029,8 +7029,9 @@ session. If the execution is resumed again, the numbers may change.
+ The current thread can be distinguished from others by a @code{#} after
+ the thread id instead of @code{:}. Without @code{l} option, it only
+ shows thread id, thread structure address and the status for each
+-thread. The status consists of 5 letters, R(run), W(wait), S(suspended),
+-O(swapped out) and N(interruptible), and if corresponding
++thread. The status consists of 6 letters, R(run), W(wait), S(suspended),
++O(swapped out), N(interruptible), and F(loating) point arithmetic used (if
++supported by the platform). If the corresponding
+ status bit is off, @code{.} is printed instead. If @code{l} option is
+ specified, more detail information is printed for each thread.
+
+--
+2.0.0
+