valgrindcallgrindkcachegrind
Callgrind: how to pass relative path to source code?
I'm using valgrind's callgrind to profile a program and then kcachegrind to view the profile data. I've copied callgrind's output file to a different machine and have a copy of the source code there, but apparently the path information of the source code is baked into callgrind's format. This means kcachegrind is looking in the wrong place:
Is there a way to pass a relative source code path so that I can profile the program on one machine but then transport the profiling data to another machine and still view the source code?
Solution
I had originally tried the sed route and that didn't work. But I looked at that solution again and the problem was that paths with '~' don't work with kcachegrind it seems.
- How to safely implement "Using Uninitialized Memory For Fun And Profit"?
- Should I worry about "Conditional jump or move depends on uninitialised value(s)"?
- Valgrind: invalid read of size 4 -> sigsegv, works fine without valgrind and in visual studio
- Enable/disable flags when doing a valgrind build
- Detailed Valgrind internals documentation
- Memory leak C++
- Memory/Address Sanitizer vs Valgrind
- How does valgrind work?
- EGL memory leak
- Valgrind memory leaks because of getaddrinfo()
- How to use valgrind on QNX platform
- Valgrind: Still Reachable Leak detected by Valgrind
- Why is my program spending 79.26% of its time in _dl_start?
- Valgrind: Memory still reachable with trivial program using <iostream>
- Why does version 3.22.0 of Valgrind-based Helgrind thread error detector reports data races and version 3.18.1 does not?
- Is it overkill to run the unit test with Valgrind?
- Memory Leak - OpenMP
- Valgrind error when loading font in SFML project
- Valgrind time limit
- Can't detect a memory leak
- Valgrind and wildcard?
- Understanding stack matching rules for custom suppressions
- How to Resolve Valgrind Errors for Uninitialized Values and Invalid Reads in a Linux Memory Scanning Program
- how do i run valgrind to a process which has super user bit on?
- Valgrind is reporting the Impossible happened using an fexecve call
- Valgrind Error: Freeing memory in the scope of function in C
- Unknown reason for malloc "corrupted top size" error
- How to examine a core file generated when program is running under valgrind
- Valgrind: dump core on first error
- Why do Valgrind-based Helgrind thread error detector and Google ThreadSanitizer (TSan) report different data race detection results?