Add a "-H" argument to kdump, which causes kdump to print an additional

field holding the threadid.  This is more useful for libthr than
libpthread, but still quite useful in libpthread as it can be used to
process interlaced records from multiple threads over the course of a
system call.

Detect old ktr_buffer values using the heuristic "if it's negative,
then it must not be a valid threadid".  This may leave something to be
desired.

MFC after:	1 month
Reviewed by:	davidxu

1 files changed, 6 insertions, 1 deletions

diff --git a/usr.bin/kdump/kdump.1 b/usr.bin/kdump/kdump.1
index 802f7cc..817f733 100644
--- a/usr.bin/kdump/kdump.1
+++ b/usr.bin/kdump/kdump.1
@@ -40,7 +40,7 @@
 .Nd display kernel trace data
 .Sh SYNOPSIS
 .Nm
-.Op Fl dEnlRT
+.Op Fl dEnlHRT
 .Op Fl f Ar trfile
 .Op Fl m Ar maxdata
 .Op Fl p Ar pid
@@ -64,6 +64,9 @@ Display elapsed timestamps (time since beginning of trace).
 .It Fl f Ar trfile
 Display the specified file instead of
 .Pa ktrace.out .
+.It Fl H
+List the thread id (tid) of the thread with each trace record, if available.
+If no thread id is available, 0 will be printed.
 .It Fl l
 Loop reading the trace file, once the end-of-file is reached, waiting for
 more data.
@@ -123,6 +126,8 @@ The first field is the PID of the process being traced.
 The second field is the name of the program being traced.
 The third field is the operation that the kernel performed
 on behalf of the process.
+If thread IDs are being printed, then an additional thread ID column will be
+added to the output between the PId field and program name field.
 .Pp
 In the first line above, the kernel executes the
 .Xr writev 2