[llvm-bugs] [Bug 35230] New: Windows ASan should avoid using SetUnhandledExceptionFilter to catch deadly signals

[via llvm-bugs]

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

            Bug ID: 35230
           Summary: Windows ASan should avoid using
                    SetUnhandledExceptionFilter to catch deadly signals
           Product: compiler-rt
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: compiler-rt
          Assignee: unassignedbugs at nondot.org
          Reporter: rnk at google.com
                CC: llvm-bugs at lists.llvm.org

The unhandled exception filter callback only runs when a debugger is not
attached to the ASan-ified process, which makes it very hard to debug ASan when
the bug is in the ASan deadly signal reporting.

It's very frustrating to continue from the crashed process and *not* be able to
step into the code in the unhandled exception filter that runs when the
debugger is not attached.

We should consider using AddVectoredExceptionHandler instead, but this presents
its own problems, because we want to ensure that ASan's handler runs after any
user handlers.

-- 
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/20171107/df5ced2f/attachment.html>