aboutsummaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorweidendo <weidendo@a5019735-40e9-0310-863c-91ae7b9d1cf9>2007-09-17 12:52:10 +0000
committerweidendo <weidendo@a5019735-40e9-0310-863c-91ae7b9d1cf9>2007-09-17 12:52:10 +0000
commit3db4322b64387313672aa525deb6c3c04fcf1134 (patch)
tree862cdf44686cad18f6a0f8ee5b32ce615f442bfd /NEWS
parente2a9ad3b71e0eccca6115349192d5e844be4eb0a (diff)
downloadvalgrind-3db4322b64387313672aa525deb6c3c04fcf1134.tar.gz
callgrind: Use directory in debug info when available
Prepend the file name of a source file with the directory if that is available. This not only gets rid of problems with the same file name used in different paths of a project, but lets the annotation work out of the box without having to specify any source directory. Works both with callgrind_annotate and KCachegrind without any changes there. Inspired by Nick's change to cachegrind doing the same thing in r6839 (and gets rid of a FIXME in the source) git-svn-id: svn://svn.valgrind.org/valgrind/trunk@6850 a5019735-40e9-0310-863c-91ae7b9d1cf9
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS3
1 files changed, 3 insertions, 0 deletions
diff --git a/NEWS b/NEWS
index ab7e29631..ddf6945b3 100644
--- a/NEWS
+++ b/NEWS
@@ -30,6 +30,9 @@ Other user-visible changes:
This means that the -I option to 'cg_annotate' should not be needed in
most cases. It also means it can correctly handle the case where two
source files in different directories have the same name.
+ The same is true for Callgrind and callgrind_annotate, respectively.
+ The benefits also apply to KCachegrind, without any further change
+ (ie. in most cases there is no configuration of source directories needed).
Developer-visible changes: