-
Notifications
You must be signed in to change notification settings - Fork 573
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
ebpf(python): update offsets for new pythons #3035
Conversation
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
PyRuntimeState_gilstate: 3112, | ||
PyRuntimeState_autoTSSkey: 1848, |
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.
I am assuming this is because it is not a "released" version?
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.
I am assuming the same :)
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.
Actually I am surprised my integration tests did not catch it, It should fail now, because test image is based on old release candidate. I will look into it.
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.
PyRuntimeState_gilstate
is not used on >= 3.13
And PyRuntimeState_autoTSSkey
is used to read pthread_key
which is an int and a counter and almost always it is zero. I am not 100% sure, but I think the test did not fail because the offset is wrong but it still read some garbage uint32=0.
fix fix add more pythons, add some offsets validation
No description provided.