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 does optimization trip valgrind false positives?
- valgrind and std::unique_ptr --- false positive or not?
- valgrind alters binary behaviour
- char** in function C and valgrind conditional jump erro
- Determining if a memory leak is a false positive
- Program crashes valgrind only in Qt Creator
- Set callgrind as default tool of valgrind
- Why does this std::weak_ptr apparently prevent freeing memory, and how can I detect this bug?
- Valgrind: disable conditional jump (or whole library) check
- Segmentation fault when converting char * to char **
- Which Valgrind tool and option to use for investigation of RAM allocation for each function?
- Valgrind gives an error "Invalid read of size 4"
- Is boost::filesystem thread-safe?
- Why does Valgrind report "uninitialized value" but not "invalid read" in my C++ vector access?
- Make a valgrind error suppression generic for a system call
- Is there a emacs valgrind interface?
- Are there known false positives issues with Valgrind?
- How to get the full call stack from Valgrind?
- Mergesort for singly-linked lists gives correct results but leaks memory
- Valgrind Massif - startpoint for memory allocation [cpp]
- Valgrind complain after modifing reference return variable from a vector in c++
- valgrind reporting invalid read with std::string
- 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?