Add a "-r" flag to ktrdump(1) to print relative timestamps when used
with "-t" rather than absolute timestamps. This allows the reader
to get a better sense of latency between events, such as time t

Add a "-r" flag to ktrdump(1) to print relative timestamps when used
with "-t" rather than absolute timestamps. This allows the reader
to get a better sense of latency between events, such as time to
schedule an interrupt thread from time the interrupt occurred. Assert
a copyright on ktrdump.c since I seem to be modifying it more than I
thought.

show more ...

Add a quiet mode to ktrdump(1): if the "-q" flag is used, don't print
the pretty text header on top of the output. Simplifies feeding the
results of tracing into a script for mechanical processing.

When the 'f' flag is passed to ktrdump(1), use 40 characters for the
"file and line" field consistently; previously, a 32-character field
length was used for the table header, which resulted in the h

When the 'f' flag is passed to ktrdump(1), use 40 characters for the
"file and line" field consistently; previously, a 32-character field
length was used for the table header, which resulted in the header
not lining up with the table.

show more ...

Remove an unused variable.

Use strlcpy() instead of strcpy() to not overflow static buffers.

- Add the -i option to read in a saved ktr file output by KTR_ALQ.

1. Add missing include of stdint.h.
2. Fix reversed arguments to strcpy.

Noticed by: davidc (2)

ktrdump is a utility to dump the ktr trace buffer from userland. It can
also be run on a core dump.

Update the projects tree to a newer FreeBSD current.

Remove unnecessary opt* definations.

Skip format flags, when parsing ktr_desc.

Really fix the relative timestamp bug. It was only incorrect for the ALQ
case. It seems entries are in reverse order when read from the kernel
memory but in the right order when read from a file (i

Really fix the relative timestamp bug. It was only incorrect for the ALQ
case. It seems entries are in reverse order when read from the kernel
memory but in the right order when read from a file (i.e. ALQ). Handle
both cases.

MFC after: 1 day

show more ...

Fix -r flag to actually work. "now" comes after "then", not vice versa.

MFC after: 1 day

Append a newline character to the usage string.

MFC after: 3 days

Sync program's usage() with manpage's SYNOPSIS.

Don't use an uninitialised variable when reading from a ktr alq file.

Add a "-r" flag to ktrdump(1) to print relative timestamps when used
with "-t" rather than absolute timestamps. This allows the reader
to get a better sense of latency between events, such as time t

Add a "-r" flag to ktrdump(1) to print relative timestamps when used
with "-t" rather than absolute timestamps. This allows the reader
to get a better sense of latency between events, such as time to
schedule an interrupt thread from time the interrupt occurred. Assert
a copyright on ktrdump.c since I seem to be modifying it more than I
thought.

show more ...

Add a quiet mode to ktrdump(1): if the "-q" flag is used, don't print
the pretty text header on top of the output. Simplifies feeding the
results of tracing into a script for mechanical processing.

When the 'f' flag is passed to ktrdump(1), use 40 characters for the
"file and line" field consistently; previously, a 32-character field
length was used for the table header, which resulted in the h

When the 'f' flag is passed to ktrdump(1), use 40 characters for the
"file and line" field consistently; previously, a 32-character field
length was used for the table header, which resulted in the header
not lining up with the table.

show more ...

Remove an unused variable.

Use strlcpy() instead of strcpy() to not overflow static buffers.

- Add the -i option to read in a saved ktr file output by KTR_ALQ.

1. Add missing include of stdint.h.
2. Fix reversed arguments to strcpy.

Noticed by: davidc (2)

ktrdump is a utility to dump the ktr trace buffer from userland. It can
also be run on a core dump.