Bug 274174 - kdump(1): list trace points directly instead of pointing to ktrace(1)
Summary: kdump(1): list trace points directly instead of pointing to ktrace(1)
Status: Open
Alias: None
Product: Documentation
Classification: Unclassified
Component: Manual Pages (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-30 13:33 UTC by Christian Weisgerber
Modified: 2023-09-30 18:24 UTC (History)
1 user (show)

See Also:

Attachments
list trace points directly in kdump(1) (1.80 KB, patch)
2023-09-30 13:33 UTC, Christian Weisgerber 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Weisgerber freebsd_committer freebsd_triage 2023-09-30 13:33:37 UTC 
Created attachment 245332 [details]
list trace points directly in kdump(1)

It's always the same:
* foobar doesn't behave as expected.
* I ktrace foobar.
* I run kdump... too much information.
* I check the kdump(1) man page, since I can't remember which letter represents which trace point.
* "See the -t option of ktrace(1)."

Sigh.  Yes, duplication is frowned on, but would it really be so bad to also list the trace points directly in kdump(1) instead of pointing to ktrace(1)?

Patch attached.