| Summary: | kdump(1): list trace points directly instead of pointing to ktrace(1) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Documentation | Reporter: | Christian Weisgerber <naddy> | ||||
| Component: | Manual Pages | Assignee: | freebsd-bugs (Nobody) <bugs> | ||||
| Status: | Open --- | ||||||
| Severity: | Affects Some People | CC: | doc | ||||
| Priority: | --- | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
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.