Crashtracker: fix a use-after-free error#2843
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #2843 +/- ##
============================================
- Coverage 81.06% 78.49% -2.58%
Complexity 2516 2516
============================================
Files 146 173 +27
Lines 14653 18682 +4029
Branches 0 975 +975
============================================
+ Hits 11879 14664 +2785
- Misses 2774 3481 +707
- Partials 0 537 +537
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
ed07274 to
027445a
Compare
BenchmarksBenchmark execution time: 2024-09-10 16:36:55 Comparing candidate commit 72358cc in PR branch Found 6 performance improvements and 1 performance regressions! Performance is the same for 171 metrics, 0 unstable metrics. scenario:EmptyFileBench/benchEmptyFileBaseline-opcache
scenario:LaravelBench/benchLaravelOverhead-opcache
scenario:MessagePackSerializationBench/benchMessagePackSerialization-opcache
scenario:PDOBench/benchPDOBaseline-opcache
scenario:PDOBench/benchPDOOverhead-opcache
scenario:PDOBench/benchPDOOverheadWithDBM-opcache
scenario:WordPressBench/benchWordPressOverhead
|
bwoebi
left a comment
There was a problem hiding this comment.
Looks right.
Do you want to also toggle the default of the LOG_BACKTRACES setting if compiled with asan (via preprocessor directive)?
I find it easier to disable the entire signal handling. WDYT? |
|
@iamluc Yeah, but then you can't run crashtracker tests with asan either and you'll have to disable tests via skipif too. |
ddf87c8 to
72358cc
Compare
Description
Reviewer checklist