[llvm-bugs] [Bug 41592] New: ASan should provide d'tor stack traces for use-after-poison.

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=41592

            Bug ID: 41592
           Summary: ASan should provide d'tor stack traces for
                    use-after-poison.
           Product: compiler-rt
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: asan
          Assignee: unassignedbugs at nondot.org
          Reporter: mitchphillips at outlook.com
                CC: llvm-bugs at lists.llvm.org

ASAN use-after-poison reports do not contain a strack trace for the destructor
of the object. This is a problem in allocation pools where the d'tor is called,
but free may be delayed. We do not get any stack trace for the deallocation,
and lifetime issues are hard to debug (https://reviews.llvm.org/D61048).

Consider this a proposal to add shadow bytes to logically identify { start of
poisoned zone, poisoned zone }. When we find a poisoned shadow byte, traverse
the shadow left to find the start of the poisoned zone.

We can store the destructor's trace in the stack depot, and use the poisoned
memory to store a pointer to the trace in the depot.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20190424/881b4f53/attachment.html>