aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authornjn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9>2009-07-14 04:24:18 +0000
committernjn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9>2009-07-14 04:24:18 +0000
commit57b87ead131791886ad79fadee65c918d1703e9b (patch)
tree3eea4b5a8181173dcb66dc82cf6de85bf7e47c34 /README
parent2b2295983ad8c8a0f4227be6c3da3a8936488fc0 (diff)
downloadvalgrind-57b87ead131791886ad79fadee65c918d1703e9b.tar.gz
Mention BBV in the README.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10446 a5019735-40e9-0310-863c-91ae7b9d1cf9
Diffstat (limited to 'README')
-rw-r--r--README5
1 files changed, 3 insertions, 2 deletions
diff --git a/README b/README
index 25652d353..067ced6ad 100644
--- a/README
+++ b/README
@@ -22,8 +22,9 @@ programs in detail. You can also use Valgrind to build new tools.
The Valgrind distribution currently includes six production-quality
tools: a memory error detector, two thread error detectors, a cache and
branch-prediction profiler, a call-graph generating cache profiler, and
-a heap profiler. It also includes one experimental tool, which detects
-out of bounds reads and writes of stack, global and heap arrays.
+a heap profiler. It also includes two experimental tools: a
+heap/stack/global array overrun detector, and a SimPoint basic block vector
+generator.
Valgrind is closely tied to details of the CPU, operating system and to
a lesser extent, compiler and basic C libraries. This makes it difficult