[llvm-bugs] [Bug 30498] New: [asan] Find a better way to print variables in stack-use-after-scope reports

[via llvm-bugs]

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

            Bug ID: 30498
           Summary: [asan] Find a better way to print variables in
                    stack-use-after-scope reports
           Product: new-bugs
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: new bugs
          Assignee: unassignedbugs at nondot.org
          Reporter: vitalybuka at google.com
                CC: llvm-bugs at lists.llvm.org
    Classification: Unclassified

For temporarily variables it's hard to guess location of the problem

Example of the current printout:
    [32, 33) 'ref.tmp.i.i.i.i'
    [48, 52) 'ref.tmp.i' <== Memory access at offset 48 is inside this variable

line information could be helpful.

-- 
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/20160922/466178ba/attachment.html>