[LLVMbugs] [Bug 9670] New: valgrind doesn't report source files and line numbers when debugging clang++ executables

[bugzilla-daemon at llvm.org]

http://llvm.org/bugs/show_bug.cgi?id=9670

           Summary: valgrind doesn't report source files and line numbers
                    when debugging clang++ executables
           Product: new-bugs
           Version: trunk
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: new bugs
        AssignedTo: unassignedbugs at nondot.org
        ReportedBy: impulze at impulze.org
                CC: llvmbugs at cs.uiuc.edu


Hi,

I found out that valgrind won't report any information when debugging an
executable created with clang++.

impulze at localhost ~ $ echo 'int main(){int *i = new int;}' > file.cc && g++
-ggdb3 file.cc && valgrind --leak-check=full ./a.out 2>&1 | grep main
==16216==    by 0x400545: main (file.cc:1)

impulze at localhost ~ $ echo 'int main(){int *i = new int;}' > file.cc && clang++
-ggdb3 file.cc && valgrind --leak-check=full ./a.out 2>&1 | grep main
==16222==    by 0x40055D: main (in /home/impulze/a.out)

Could anyone tell me whose fault it is or if more information is required to
gather the entity that's causing the issue?

Thanks in advance.

-- 
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.