API Change / Addition to sentry_capture_minidump#1138
API Change / Addition to sentry_capture_minidump#1138supervacuus merged 21 commits intogetsentry:masterfrom
Conversation
supervacuus
left a comment
There was a problem hiding this comment.
Please add a changelog entry using the header ##Unreleased if it is not there yet. Then, add a section **Breaking changes**: to list the changes.
...for users whose editor does not pick up `.editorconfig`.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1138 +/- ##
==========================================
+ Coverage 82.66% 82.79% +0.12%
==========================================
Files 53 53
Lines 7927 7939 +12
Branches 1239 1239
==========================================
+ Hits 6553 6573 +20
+ Misses 1263 1256 -7
+ Partials 111 110 -1 |
…ntation. The fix also visualizes the event_id generation and capture validity discrepancy much better. The bug in the proposed implementation was retrieving the event_id from the envelope after it had been captured. In this case we have no control over the validity of the envelope because the capture function takes ownership and frees the envelope. Retrieving the event_id after the capture is thus a race that leads to a UAF. We can only safely retrieve the event_id from the moment where we create the envelope from the event (which is also where the event_id is generated). Of course after this a few things can still go wrong, which is why we cannot maintain the event_id as return value, but only return it if we reached the capture. In all other cases we return a nil UUID, as specified in the comment.
|
Looking into this failure in tests
|
|
And these |
There is no need, @zsd4yr. I had to rewrite the proposed implementation (and parts of the initial implementation). I'll take over from here. Thanks! |
…inside the options scope. Ensure to track even for faile item and failed envelope creation.
|
Thanks @supervacuus ! |
also: freeing envelopes also decrements the refcount of the event they were created from.
|
@supervacuus Thanks for getting this across the finish line! When will the next drop be available? I'll update our fork with this :) |
See #1135