| #
96f4be88
|
| 31-May-2025 |
Konstantin Belousov <kib@FreeBSD.org> |
ktrace(1): teach about KTR_EXTERR
Reviewed by: brooks Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D50633
|
| #
596ee234
|
| 07-Jan-2025 |
Mark Johnston <markj@FreeBSD.org> |
ktrace: Make -t t trace struct arrays as well as structs
Otherwise there is no specific -t option which captures struct arrays.
MFC after: 1 week
|
| #
2a657b4e
|
| 17-Nov-2024 |
Jose Luis Duran <jlduran@FreeBSD.org> |
ktrace.1: Add ARGS and ENVS as default trace points
After commit 65a4daeaf324 ("ktrace: log execve(2) arguments and environment"), "a" and "e" are part of the default set of trace points.
Reviewed
ktrace.1: Add ARGS and ENVS as default trace points
After commit 65a4daeaf324 ("ktrace: log execve(2) arguments and environment"), "a" and "e" are part of the default set of trace points.
Reviewed by: markj Approved by: emaste (mentor) Fixes: 65a4daeaf324 ("ktrace: log execve(2) arguments and environment") Differential Revision: https://reviews.freebsd.org/D47648
show more ...
|
| #
65a4daea
|
| 15-Oct-2024 |
Artem Hevorhian <artemhevorhian@gmail.com> |
ktrace: log execve(2) arguments and environment
Two new events KTR_ARGS and KTR_ENV can be used to trace arguments of execve(2).
Reviewed by: glebius Differential Revision: https://reviews.freebsd
ktrace: log execve(2) arguments and environment
Two new events KTR_ARGS and KTR_ENV can be used to trace arguments of execve(2).
Reviewed by: glebius Differential Revision: https://reviews.freebsd.org/D47127
show more ...
|
| #
0277c0c6
|
| 11-Jun-2024 |
Ed Maste <emaste@FreeBSD.org> |
ktrace(1): add more xrefs
Following commit a87651e2ff18 add xrefs to intro(2) and sigaction(2), and use a consistent form.
Suggested by: kib, arrowd Reviewed by: kib (earlier) Sponsored by: The Fre
ktrace(1): add more xrefs
Following commit a87651e2ff18 add xrefs to intro(2) and sigaction(2), and use a consistent form.
Suggested by: kib, arrowd Reviewed by: kib (earlier) Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D45555
show more ...
|
| #
a87651e2
|
| 10-Jun-2024 |
Ed Maste <emaste@FreeBSD.org> |
ktrace(1): add xref to namei(9)
namei was mistaken for a typo (see GitHub pull request #1284). Add an xref to make it clear.
Reviewed by: imp Sponsored by: The FreeBSD Foundation Differential Revi
ktrace(1): add xref to namei(9)
namei was mistaken for a typo (see GitHub pull request #1284). Add an xref to make it clear.
Reviewed by: imp Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D45546
show more ...
|
| #
f239db48
|
| 24-Apr-2024 |
Jake Freeland <jfree@FreeBSD.org> |
ktrace: Remove CAPFAIL from default trace points
The CAPFAIL tracepoint was recently extended to report ECAPMODE capability violations for processes that do not enter capability mode. This allows d
ktrace: Remove CAPFAIL from default trace points
The CAPFAIL tracepoint was recently extended to report ECAPMODE capability violations for processes that do not enter capability mode. This allows developers that are interested in Capsicumizing their programs to determine where violations are being raised.
Previously, CAPFAIL only produced output for processes using Capsicum(4) capabilties. Thus, most ktrace users never received log output from the trace point. With the recent changes, this is no longer the case.
Having this trace point enabled by default will produce output for all processes that use syscalls that are not permitted in capability mode. This may lead to confusion for users that are not familiar with the feature. Remove KTRFAC_CAPFAIL from ktrace's default points to avoid this.
Approved by: markj (mentor) Reviewed by: markj MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D44887
show more ...
|
| #
4f2ada0d
|
| 24-Apr-2024 |
Jake Freeland <jfree@FreeBSD.org> |
ktrace: Describe CAPFAIL trace point in man page
Update the ktrace(1) man page to describe the recently improved capability failure tracing.
Approved by: markj (mentor) Reviewed by: markj MFC after
ktrace: Describe CAPFAIL trace point in man page
Update the ktrace(1) man page to describe the recently improved capability failure tracing.
Approved by: markj (mentor) Reviewed by: markj MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D44886
show more ...
|
| #
bdcbfde3
|
| 23-Nov-2023 |
Warner Losh <imp@FreeBSD.org> |
usr.bin: Remove ancient SCCS tags.
Remove ancient SCCS tags from the tree, automated scripting, with two minor fixup to keep things compiling. All the common forms in the tree were removed with a pe
usr.bin: Remove ancient SCCS tags.
Remove ancient SCCS tags from the tree, automated scripting, with two minor fixup to keep things compiling. All the common forms in the tree were removed with a perl script.
Sponsored by: Netflix
show more ...
|
| #
b2c76c41
|
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: one-line nroff pattern
Remove /^\.\\"\s*\$FreeBSD\$$\n/
|
| #
c5c3ba6b
|
| 03-Sep-2019 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r351317 through r351731.
|
| #
90a7bed4
|
| 26-Aug-2019 |
Edward Tomasz Napierala <trasz@FreeBSD.org> |
Make it clear what the userland traces are in the ktrace(1) man page.
MFC after: 2 weeks
|
| #
96f4be88
|
| 31-May-2025 |
Konstantin Belousov <kib@FreeBSD.org> |
ktrace(1): teach about KTR_EXTERR
Reviewed by: brooks Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D50633
|
| #
596ee234
|
| 07-Jan-2025 |
Mark Johnston <markj@FreeBSD.org> |
ktrace: Make -t t trace struct arrays as well as structs
Otherwise there is no specific -t option which captures struct arrays.
MFC after: 1 week
|
| #
2a657b4e
|
| 17-Nov-2024 |
Jose Luis Duran <jlduran@FreeBSD.org> |
ktrace.1: Add ARGS and ENVS as default trace points
After commit 65a4daeaf324 ("ktrace: log execve(2) arguments and environment"), "a" and "e" are part of the default set of trace points.
Reviewed
ktrace.1: Add ARGS and ENVS as default trace points
After commit 65a4daeaf324 ("ktrace: log execve(2) arguments and environment"), "a" and "e" are part of the default set of trace points.
Reviewed by: markj Approved by: emaste (mentor) Fixes: 65a4daeaf324 ("ktrace: log execve(2) arguments and environment") Differential Revision: https://reviews.freebsd.org/D47648
show more ...
|
| #
65a4daea
|
| 15-Oct-2024 |
Artem Hevorhian <artemhevorhian@gmail.com> |
ktrace: log execve(2) arguments and environment
Two new events KTR_ARGS and KTR_ENV can be used to trace arguments of execve(2).
Reviewed by: glebius Differential Revision: https://reviews.freebsd
ktrace: log execve(2) arguments and environment
Two new events KTR_ARGS and KTR_ENV can be used to trace arguments of execve(2).
Reviewed by: glebius Differential Revision: https://reviews.freebsd.org/D47127
show more ...
|
| #
0277c0c6
|
| 11-Jun-2024 |
Ed Maste <emaste@FreeBSD.org> |
ktrace(1): add more xrefs
Following commit a87651e2ff18 add xrefs to intro(2) and sigaction(2), and use a consistent form.
Suggested by: kib, arrowd Reviewed by: kib (earlier) Sponsored by: The Fre
ktrace(1): add more xrefs
Following commit a87651e2ff18 add xrefs to intro(2) and sigaction(2), and use a consistent form.
Suggested by: kib, arrowd Reviewed by: kib (earlier) Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D45555
show more ...
|
| #
a87651e2
|
| 10-Jun-2024 |
Ed Maste <emaste@FreeBSD.org> |
ktrace(1): add xref to namei(9)
namei was mistaken for a typo (see GitHub pull request #1284). Add an xref to make it clear.
Reviewed by: imp Sponsored by: The FreeBSD Foundation Differential Revi
ktrace(1): add xref to namei(9)
namei was mistaken for a typo (see GitHub pull request #1284). Add an xref to make it clear.
Reviewed by: imp Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D45546
show more ...
|
| #
f239db48
|
| 24-Apr-2024 |
Jake Freeland <jfree@FreeBSD.org> |
ktrace: Remove CAPFAIL from default trace points
The CAPFAIL tracepoint was recently extended to report ECAPMODE capability violations for processes that do not enter capability mode. This allows d
ktrace: Remove CAPFAIL from default trace points
The CAPFAIL tracepoint was recently extended to report ECAPMODE capability violations for processes that do not enter capability mode. This allows developers that are interested in Capsicumizing their programs to determine where violations are being raised.
Previously, CAPFAIL only produced output for processes using Capsicum(4) capabilties. Thus, most ktrace users never received log output from the trace point. With the recent changes, this is no longer the case.
Having this trace point enabled by default will produce output for all processes that use syscalls that are not permitted in capability mode. This may lead to confusion for users that are not familiar with the feature. Remove KTRFAC_CAPFAIL from ktrace's default points to avoid this.
Approved by: markj (mentor) Reviewed by: markj MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D44887
show more ...
|
| #
4f2ada0d
|
| 24-Apr-2024 |
Jake Freeland <jfree@FreeBSD.org> |
ktrace: Describe CAPFAIL trace point in man page
Update the ktrace(1) man page to describe the recently improved capability failure tracing.
Approved by: markj (mentor) Reviewed by: markj MFC after
ktrace: Describe CAPFAIL trace point in man page
Update the ktrace(1) man page to describe the recently improved capability failure tracing.
Approved by: markj (mentor) Reviewed by: markj MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D44886
show more ...
|
| #
bdcbfde3
|
| 23-Nov-2023 |
Warner Losh <imp@FreeBSD.org> |
usr.bin: Remove ancient SCCS tags.
Remove ancient SCCS tags from the tree, automated scripting, with two minor fixup to keep things compiling. All the common forms in the tree were removed with a pe
usr.bin: Remove ancient SCCS tags.
Remove ancient SCCS tags from the tree, automated scripting, with two minor fixup to keep things compiling. All the common forms in the tree were removed with a perl script.
Sponsored by: Netflix
show more ...
|
| #
b2c76c41
|
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: one-line nroff pattern
Remove /^\.\\"\s*\$FreeBSD\$$\n/
|
| #
c5c3ba6b
|
| 03-Sep-2019 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r351317 through r351731.
|
| #
90a7bed4
|
| 26-Aug-2019 |
Edward Tomasz Napierala <trasz@FreeBSD.org> |
Make it clear what the userland traces are in the ktrace(1) man page.
MFC after: 2 weeks
|
| #
0275f9db
|
| 11-Aug-2017 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
Merge ^/head r321383 through r322397.
|