GWP-ASan: Change double free crash analysis logic
Currently, the crash analyzer determines if a crash is related to GWP-ASan by checking to see if the exception address was in the GWP-ASan region. This can lead to some messy logic, such as requiring a double free to intentionally access the invalid allocation to crash which can be racy. Currently if two threads race a double free Thread 1 marks an allocation freed but not yet inaccessible and Thread 2 can fail to crash on accessing the page. Instead, update the allocator to store the double free address if a double free occurs and trap and have the crash handler to use that address as the source of the crash. Bug: 925447 Change-Id: Ia34a10c53d3d4a78c5bf82db671e3d0bb87ea4b9 Reviewed-on: https://chromium-review.googlesource.com/c/1435984 Auto-Submit: Vlad Tsyrklevich <vtsyrklevich@chromium.org> Reviewed-by:Vitaly Buka <vitalybuka@chromium.org> Commit-Queue: Vlad Tsyrklevich <vtsyrklevich@chromium.org> Cr-Commit-Position: refs/heads/master@{#626367}
Showing
Please register or sign in to comment