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
    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.
llvm-bugs mailing list

Reply via email to