diff options
| author | sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> | 2002-07-25 22:45:35 +0000 |
|---|---|---|
| committer | sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> | 2002-07-25 22:45:35 +0000 |
| commit | 3a359feabd0910769e9cf0c4fb28c2ed643153a8 (patch) | |
| tree | 3b90da6775a6ea0c632bd2b8938bb8d94d577ed5 /README | |
| parent | c50cf8d7ea16e8a48a4e0ffe0bf7e27ae458b0ec (diff) | |
Final caveats for 1.0.0.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@536 a5019735-40e9-0310-863c-91ae7b9d1cf9
Diffstat (limited to 'README')
| -rw-r--r-- | README | 10 |
1 files changed, 8 insertions, 2 deletions
@@ -1,6 +1,6 @@ -Release notes for Valgrind, version 1.0 -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Release notes for Valgrind, version 1.0.0 +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ KDE3 developers: please read also README_KDE3_FOLKS for guidance about how to debug KDE3 applications with Valgrind. @@ -9,6 +9,12 @@ please read README_PACKAGERS. It contains some important information. For instructions on how to build/install, see the end of this file. +Valgrind works best on systems with glibc-2.1.X or 2.2.X, and with gcc +versions prior to 3.1. gcc-3.1 works, but generates code which causes +valgrind to report many false errors. For now, try to use a gcc prior +to 3.1; if you can't, at least compile your application without +optimisation. Valgrind-1.0.X also can't handle glibc-2.3.X systems. + Executive Summary ~~~~~~~~~~~~~~~~~ |