blob: 6c7674f9c65b11a75dc337935fdfaaad92421662 [file] [log] [blame]
sewardjde4a1d02002-03-22 01:27:54 +00001
sewardj3a359fe2002-07-25 22:45:35 +00002Release notes for Valgrind, version 1.0.0
3~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
nethercote382a8922003-12-02 15:25:39 +00004> We're well past 1.0.0. I propose removing the version number here;
5> it doesn't contribute anything, and just gets out-of-date.
6
sewardjde4a1d02002-03-22 01:27:54 +00007KDE3 developers: please read also README_KDE3_FOLKS for guidance
8about how to debug KDE3 applications with Valgrind.
9
nethercote382a8922003-12-02 15:25:39 +000010> I propose removing README_KDE3_FOLKS, and this reference to it; I
11> think Valgrind has been around long enough that KDE developers don't
12> need separate instructions.
sewardj365a8512002-07-01 08:30:05 +000013
nethercote382a8922003-12-02 15:25:39 +000014[snip]
sewardjde4a1d02002-03-22 01:27:54 +000015
sewardj3a359fe2002-07-25 22:45:35 +000016Valgrind works best on systems with glibc-2.1.X or 2.2.X, and with gcc
17versions prior to 3.1. gcc-3.1 works, but generates code which causes
18valgrind to report many false errors. For now, try to use a gcc prior
19to 3.1; if you can't, at least compile your application without
20optimisation. Valgrind-1.0.X also can't handle glibc-2.3.X systems.
21
nethercote382a8922003-12-02 15:25:39 +000022> Out of date: I think glibc-2.3.X is ok, right? Also gcc-3.1 is ok?
sewardjde4a1d02002-03-22 01:27:54 +000023
24Executive Summary
25~~~~~~~~~~~~~~~~~
sewardjde4a1d02002-03-22 01:27:54 +000026
nethercote382a8922003-12-02 15:25:39 +000027> This summary doesn't account for the core/tool split. Should be
28> similar to the overview on the website.
sewardjde4a1d02002-03-22 01:27:54 +000029
nethercote382a8922003-12-02 15:25:39 +000030[snip]
sewardjde4a1d02002-03-22 01:27:54 +000031
32Valgrind is closely tied to details of the CPU, operating system and
33to a less extent, compiler and basic C libraries. This makes it
34difficult to make it portable, so I have chosen at the outset to
35concentrate on what I believe to be a widely used platform: Red Hat
36Linux 7.2, on x86s. I believe that it will work without significant
37difficulty on other x86 GNU/Linux systems which use the 2.4 kernel and
sewardj365a8512002-07-01 08:30:05 +000038GNU libc 2.2.X, for example SuSE 7.1 and Mandrake 8.0. This version
391.0 release is known to work on Red Hats 6.2, 7.2 and 7.3, at the very
40least.
sewardjde4a1d02002-03-22 01:27:54 +000041
nethercote382a8922003-12-02 15:25:39 +000042> Out of date... could make more generic, eg. works on most/all common
43> Linux distros
44
sewardjde4a1d02002-03-22 01:27:54 +000045Valgrind is licensed under the GNU General Public License, version 2.
njn25e49d8e72002-09-23 09:36:25 +000046Read the file COPYING in the source distribution for details.
sewardjde4a1d02002-03-22 01:27:54 +000047
48
49Documentation
50~~~~~~~~~~~~~
51A comprehensive user guide is supplied. Point your browser at
52docs/index.html. If your browser doesn't like frames, point it
sewardj40183922002-06-19 20:52:32 +000053instead at docs/manual.html. There's also detailed, although somewhat
54out of date, documentation of how valgrind works, in
55docs/techdocs.html.
sewardjde4a1d02002-03-22 01:27:54 +000056
nethercote382a8922003-12-02 15:25:39 +000057> These paths are incorrect.
sewardjde4a1d02002-03-22 01:27:54 +000058
nethercote382a8922003-12-02 15:25:39 +000059[snip]
sewardjde4a1d02002-03-22 01:27:54 +000060
sewardjde4a1d02002-03-22 01:27:54 +000061Julian Seward (jseward@acm.org)
sewardj365a8512002-07-01 08:30:05 +0000621 July 2002
nethercote382a8922003-12-02 15:25:39 +000063
64> out of date, I suggest removing the date, and saying "report bugs to
65> valgrind.kde.org" or similar.
66