-
Notifications
You must be signed in to change notification settings - Fork 43
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
fix(*) catch and fix more GC corner cases #178
Conversation
4c7cc18
to
8abdb67
Compare
ffi_gc(got_ref, stack_lib.gc_of("GENERAL_NAME")) | ||
got = ffi_cast("GENERAL_NAMES*", got_ref)''', | ||
got = ffi_cast("GENERAL_NAMES*", got_ref) | ||
ffi_gc(got, stack_lib.gc_of("GENERAL_NAME"))''', |
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.
If you have set ffi.gc function for got_ref in the upper layer function, then the underlying object would be freeed two times by the ffi.gc.
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.
It won't be double free because got_ref
is a opaque pointer, it doesn't have GC handler to free the pointed object. we only have gc handler for got
.
store:check_revocation
…name, info_access and dist_points
@zhuizhuhaomeng The tests are now green with the new valgrind setup, I'm going to merge this and looking to make the tests faster. Any suggestions are welcomed! And thanks for bringing this up, it's also a learning |
No description provided.