libbpf-tools/sigsnoop: Allow to trace a signal list #5055
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ZhangYet
requested review from
drzaeus77,
goldshtn,
yonghong-song,
4ast,
brendangregg and
davemarchevsky
as code owners
ZhangYet
force-pushed
the
dante-dev
branch
3 times, most recently
from
801c313
to
ea19b4d
Compare
ZhangYet
force-pushed
the
dante-dev
branch
2 times, most recently
from
356e4f0
to
c9c0bab
Compare
tools/killsnoop supports a signal list(47d7263), it's reasonable to support the same feature in libbpf-tools/sigsnoop. Signed-off-by: Dantezy <[email protected]>
I have fixed them. Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
tools/killsnoop supports a signal list(47d7263),
it's reasonable to support the same feature in libbpf-tools/sigsnoop.