|
From: Nicholas N. <nj...@cs...> - 2005-03-01 02:59:01
|
Hi, I've added a new document, called the Valgrind Quick Start, to the Valgrind site. Read it at valgrind.kde.org/docs.html. It contains the minimum amount of information you need to know to start using Memcheck, Valgrind's memory checking tool. Hopefully people will find this useful. Comments are welcome. N |
|
From: Olly B. <ol...@su...> - 2005-03-02 18:58:22
|
On 2005-03-01, Nicholas Nethercote <nj...@cs...> wrote: > I've added a new document, called the Valgrind Quick Start, to the > Valgrind site. Read it at valgrind.kde.org/docs.html. Looks an excellent introduction. > Hopefully people will find this useful. Comments are welcome. It might be worth noting that you can only valgrind 32 bit x86 code on an x86_64 currently, but that x86_64 is being worked on. That seems to be the most commonly asked question on this list recently! Where you say: "Your program will run much slower (eg. 20 to 30 times) than normal." I wonder if it would be useful to also note that it'll require slightly more than double the amount of memory for data, and some for instrumented code, and to point people to addrcheck as a faster, less memory hungry alternative. My final thought is to make it HTML, so you can add links to appropriate parts of the manual for finding more information. Cheers, Olly |