-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable clone3 #1971
Merged
Merged
Enable clone3 #1971
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
erthalion
force-pushed
the
fix/clone3
branch
from
November 26, 2024 11:18
e6472ff
to
076bf2a
Compare
erthalion
force-pushed
the
fix/clone3
branch
2 times, most recently
from
November 26, 2024 14:06
f9ddeb5
to
6adb950
Compare
Molter73
reviewed
Nov 26, 2024
erthalion
force-pushed
the
fix/clone3
branch
2 times, most recently
from
December 3, 2024 09:26
53b7967
to
9673e01
Compare
erthalion
force-pushed
the
fix/clone3
branch
2 times, most recently
from
December 10, 2024 09:44
7b8eff9
to
fa9fad9
Compare
erthalion
force-pushed
the
fix/clone3
branch
from
December 10, 2024 16:50
fa9fad9
to
905bce2
Compare
Originally we've excluded clone3, which wasn't present on some older platforms. But now it's getting used by newer glibc, which means that we're missing information about threads. It plays some visible role only when threads are exiting, e.g. in a weird situation if a thread will do exec, all the threads in the thread group are going to be stopped, leaving only one running exec. This is visible in the resolved file path for the event.
erthalion
force-pushed
the
fix/clone3
branch
from
December 12, 2024 09:58
16fbcc6
to
352f47a
Compare
Stringy
reviewed
Dec 12, 2024
erthalion
force-pushed
the
fix/clone3
branch
from
December 13, 2024 09:55
352f47a
to
e5257d2
Compare
Stringy
approved these changes
Dec 17, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
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.
Description
Originally we've excluded clone3, which wasn't present on some older
platforms. But now it's getting used by newer glibc, which means that
we're missing information about threads. It plays some visible role only
when threads are exiting, e.g. in a weird situation if a thread will do
exec, all the threads in the thread group are going to be stopped,
leaving only one running exec. This is visible in the resolved file path
for the event.
Also includes a small CI improvement, allowing use of trace log level
in the debug mode.
Checklist
Automated testing
Testing Performed
Local testing to verify which event we receive with clone and clone3.