User Details
User Details
- User Since
- Feb 1 2021, 1:41 PM (96 w, 3 d)
- Availability
- Available
Aug 8 2022
Aug 8 2022
jap added a comment to T6060: segfault (NULL-pointer) when inspecting gpg Context after exception (python).
Not sure if that is the complete fix - if you do something like:
with gpg.Context(...) as context:
...
... cause an exception after the context has been closed ...then context will still be a valid reference to the gpg.Context instance, and may cause segfaults when something tries to access things inside it (f.e. for serialisation).
I like your previous solution with the accessor checks, because that actually fixes the issue.
Stylistically, maybe __del__ should just be renamed to cleanup or free, and then make sure to call that function from both __exit__ and __del__.
jap added a comment to T6060: segfault (NULL-pointer) when inspecting gpg Context after exception (python).
Can confirm, we've been running into this as well, but never filed a bug report. Our solution is to have this in our codebase:
Feb 21 2022
Feb 21 2022
Feb 10 2022
Feb 10 2022
jap added projects to T5825: [gpgme] [python] possible dangling reference to passphrase: gpgme, patch.
jap added a comment to T5825: [gpgme] [python] possible dangling reference to passphrase.
Feb 9 2021
Feb 9 2021
jap added a comment to T5292: regression: no longer possible to get signatures from decrypt from unknown keys.
Feb 1 2021
Feb 1 2021
jap added a comment to T5284: Allow gpgme to export w/o attributes.
Not exactly the answer I was hoping for..