|
From: Nicholas N. <nj...@ca...> - 2004-04-21 07:25:49
|
CVS commit by nethercote: Remove Annelid; it can go under "Other", and no-one is using it anyway. M +0 -1 survey2 1.8 --- devel-home/valgrind/survey2 #1.7:1.8 @@ -102,5 +102,4 @@ Calltree/KCachegrind : Massif : -Annelid : other : |
|
From: Nicholas N. <nj...@ca...> - 2004-04-26 08:13:28
|
CVS commit by nethercote: Added GNUnet, libExtractor M +6 -0 users.html 1.62 --- devel-home/valgrind/users.html #1.61:1.62 @@ -394,4 +394,7 @@ <dd>A cross-platform Jabber client designed for the Jabber power user. +<dt><a href=" http://www.ovmj.org/GNUnet/">GNUnet</a> +<dd>A secure peer-to-peer file sharing framework. + <dt><a href="http://gtk-gnutella.sf.net/">Gtk-Gnutella</a> <dd>A P2P application for the Gnutella network that aims for high uptimes. @@ -440,4 +443,7 @@ <dt><a href="http://www.willamowius.de/sd.html">Speed Dragon Tools</a> <dd>Programming tools for the Speed Dragon ISDN PBX. + +<dt><a href="http://www.ovmj.org/libextractor/">libExtractor</a> +<dd>A library for extracting metadata from files. </dl> |
|
From: Nicholas N. <nj...@ca...> - 2004-04-29 11:17:10
|
CVS commit by nethercote: fix typo M +1 -1 articles.html 1.10 --- devel-home/valgrind/articles.html #1.9:1.10 @@ -67,5 +67,5 @@ <li><a href="http://developers.slashdot.org/article.pl?sid=02/07/28/1833225">Valgrind - 1.0.0 Released"</a>. + 1.0.0 Released</a>. Slashdot, July 28, 2002. </ul> |
|
From: Nicholas N. <nj...@ca...> - 2004-04-29 11:19:07
|
CVS commit by nethercote:
Added picture of bronze merit award
M +7 -0 awards.html 1.2
--- devel-home/valgrind/awards.html #1.1:1.2
@@ -12,9 +12,16 @@
<a href="http://opensource.org/OSA/">Open Source Award</a>.
</ul>
+
<p>
See Valgrind's <a href="http://freshmeat.net/stats/#rating">ranking</a> among
the best projects at <a href="http://freshmeat.net">freshmeat.net</a>. (At the
time of writing, Valgrind was number 6.)
+
<p>
+<a href="http://opensource.org/OSA/">
+ <img src="http://opensource.org/osa/osamerit.png"
+ border="0"
+ alt="open source award logo">
+</a>
<?php
|
|
From: Nicholas N. <nj...@ca...> - 2004-04-29 11:34:11
|
CVS commit by nethercote: Added MICO M +4 -0 users.html 1.63 --- devel-home/valgrind/users.html #1.62:1.63 @@ -446,4 +446,8 @@ <dt><a href="http://www.ovmj.org/libextractor/">libExtractor</a> <dd>A library for extracting metadata from files. + +<dt><a href="http://www.mico.org/">MICO</a> +<dd>A freely available and fully compliant C++ implementation of the CORBA + standard. </dl> |
|
From: Nicholas N. <nj...@ca...> - 2004-05-13 19:11:57
|
CVS commit by nethercote: Add a survey question about how Valgrind was obtained. Strengthen email address obfuscation (probably only paranoic voodoo). M +4 -4 contact.html 1.3 M +1 -1 downloads.html 1.12 M +12 -1 survey2 1.9 M +1 -1 users.html 1.64 --- devel-home/valgrind/contact.html #1.2:1.3 @@ -7,7 +7,7 @@ <h3>General</h3> Praise, abuse, ideas, etc, can be sent to: -<br>Julian Seward (jseward at acm dot org) -<br>Nick Nethercote (njn25 at cam dot ac dot uk) -<br>Jeremy Fitzhardinge (jeremy at goop dot org) +<br>Julian Seward (jseward at acm org) +<br>Nick Nethercote (njn25 at cam ac uk) +<br>Jeremy Fitzhardinge (jeremy at goop org) <p> If you want to give detailed, general feedback, please fill out our @@ -17,5 +17,5 @@ <h3>Website</h3> Please send feedback about this website to Nick Nethercote -(njn25 at cam dot ac dot uk). +(njn25 at cam ac uk). <p> --- devel-home/valgrind/downloads.html #1.11:1.12 @@ -109,5 +109,5 @@ fully supported. Leak checking does not work at the moment. <p> -A big thanks to Adam Gundy (arg at cyberscience dot com) for this. +A big thanks to Adam Gundy (arg at cyberscience com) for this. <p> --- devel-home/valgrind/survey2 #1.8:1.9 @@ -92,4 +92,15 @@ comments: +# In what form did you/do you obtain Valgrind? +# (Select all the options that are appropriate.) + +source, from CVS [ ] +source, from website [ ] +pre-built version (eg. RPM) [ ] +already installed on system [ ] +other : + +comments: + # Which Valgrind tools do you use? Estimate the proportion of your Valgrind # usage each tool accounts for. @@ -297,5 +308,5 @@ #---------------------------------------------------------------------------- -# Please send completed surveys to njn25 at cam dot ac dot uk. +# Please send completed surveys to njn25 at cam ac uk. # # Thank you for your time and support. --- devel-home/valgrind/users.html #1.63:1.64 @@ -453,5 +453,5 @@ -Please contact Nick Nethercote (njn25 at cam dot ac dot uk) if you are happy to +Please contact Nick Nethercote (njn25 at cam ac uk) if you are happy to have your project added to this list. Please provide a URL and a short description of your project. |
|
From: Nicholas N. <nj...@ca...> - 2004-05-18 09:38:58
|
CVS commit by nethercote: Added Beosim. M +3 -0 users.html 1.65 --- devel-home/valgrind/users.html #1.64:1.65 @@ -139,4 +139,7 @@ <dt><a href="http://vxl.sf.net/">VXL</a> <dd>C++ Libraries for computer vision research and implementation. + +<dt><a href="http://www.parl.clemson.edu/~wjones/research/index.html">Beosim</a> +<dd>A Beowulf grid simulator. </dl> |
|
From: Nicholas N. <nj...@ca...> - 2004-05-30 08:48:23
|
CVS commit by nethercote:
Added ROOT
M +3 -0 users.html 1.66
--- devel-home/valgrind/users.html #1.65:1.66
@@ -110,4 +110,7 @@
simulation software.
+<dt><a href="http://root.cern.ch/home/">ROOT</a>
+<dd>A widely-used data access, analysis and visualisation system.
+
<dt><a href="http://www.hlrs.de/organization/pds/projects/pacx-mpi/">PACX-MPI</a>
<dd>A library for running parallel application on clusters connected
|
|
From: Nicholas N. <nj...@ca...> - 2004-06-02 20:26:22
|
CVS commit by nethercote: Added Xsupplicant. M +3 -0 users.html 1.67 --- devel-home/valgrind/users.html #1.66:1.67 @@ -336,4 +336,7 @@ <dt><a href="http://www.nomachine.com/developers.php">NX</a> <dd>X Window compression software. + +<dt><a href="http://www.open1x.org">Xsupplicant</a> +<dd>An 802.1X client for Linux. </dl> |
|
From: Nicholas N. <nj...@ca...> - 2004-06-02 20:59:54
|
CVS commit by nethercote: Added info about MIT Daikon/Kvasir project. M +12 -5 related.html 1.15 --- devel-home/valgrind/related.html #1.14:1.15 @@ -102,9 +102,16 @@ <h3>Other</h3> -The University of New Mexico's -<a href="http://www.cs.unm.edu/~gbarrant/RISE.html">RISE project</a> -used Valgrind to implement randomized instruction set emulation, in order to -disrupt binary code injection attacks. -<p> +Valgrind has been used as the starting point for various research projects. +<ul> +<li>The University of New Mexico's + <a href="http://www.cs.unm.edu/~gbarrant/RISE.html">RISE project</a> + used Valgrind to implement randomized instruction set emulation, in order + to disrupt binary code injection attacks. + <p> +<li>MIT's <a href="http://pag.csail.mit.edu/daikon/">Daikon</a> invariant + detection system uses Valgrind to implement a trace-gathering tool named + Kvasir. + <p> +</ul> <?php |
|
From: Nicholas N. <nj...@ca...> - 2004-06-04 07:58:29
|
CVS commit by nethercote: Added notes about statically linked multi-threaded programs not working. M +9 -6 faq.html 1.4 --- devel-home/valgrind/faq.html #1.3:1.4 @@ -228,10 +228,13 @@ For versions 2.1.1 and later: -Valgrind does now work with static binaries, although beware that some -of the tools won't operate as well as normal, because they have access -to less information about how the program runs. Eg. Memcheck will miss -some errors that it would otherwise find. This is because Valgrind -doesn't replace malloc() and friends with its own versions. It's best -if your program is dynamically linked with glibc. +Valgrind does now work with single-threaded static binaries, although +beware that some of the tools won't operate as well as normal, because +they have access to less information about how the program runs. Eg. +Memcheck will miss some errors that it would otherwise find. This is +because Valgrind doesn't replace malloc() and friends with its own +versions. Valgrind won't work with multi-threaded static binaries, +as Valgrind won't be able to use its own pthreads implementation. + +In short, it's best if your program is dynamically linked. ----------------------------------------------------------------- |
|
From: Nicholas N. <nj...@ca...> - 2004-06-07 09:22:09
|
CVS commit by nethercote:
Added naim.
M +4 -1 users.html 1.68
--- devel-home/valgrind/users.html #1.67:1.68
@@ -400,8 +400,11 @@
multiple connections.
+<dt><a href="http://naim.n.ml.org/">naim</a>
+<dd>An instant messaging console client for AIM, ICQ, IRC, and The lily CMC.
+
<dt><a href="http://psi.affinix.com/">Psi</a>
<dd>A cross-platform Jabber client designed for the Jabber power user.
-<dt><a href=" http://www.ovmj.org/GNUnet/">GNUnet</a>
+<dt><a href="http://www.ovmj.org/GNUnet/">GNUnet</a>
<dd>A secure peer-to-peer file sharing framework.
|
|
From: Nicholas N. <nj...@ca...> - 2004-07-05 11:00:08
|
CVS commit by nethercote: Remove out-of-date info. M +0 -5 awards.html 1.3 --- devel-home/valgrind/awards.html #1.2:1.3 @@ -14,9 +14,4 @@ <p> -See Valgrind's <a href="http://freshmeat.net/stats/#rating">ranking</a> among -the best projects at <a href="http://freshmeat.net">freshmeat.net</a>. (At the -time of writing, Valgrind was number 6.) - -<p> <a href="http://opensource.org/OSA/"> <img src="http://opensource.org/osa/osamerit.png" |
|
From: Nicholas N. <nj...@ca...> - 2004-07-07 22:15:32
|
CVS commit by nethercote: Added Worldforge M +3 -0 users.html 1.69 --- devel-home/valgrind/users.html #1.68:1.69 @@ -417,4 +417,7 @@ <dt><a href="http://bidwatcher.sf.net/">Bidwatcher</a> <dd>An eBay auction listing tracker. + +<dt><a href="http://www.worldforge.com/">Worldforge</a> +<dd>A web search engine and portal. </dl> |
|
From: Nicholas N. <nj...@ca...> - 2004-07-07 23:05:40
|
CVS commit by nethercote: Mixed up worldforge.org and worldforge.com. M +2 -2 users.html 1.70 --- devel-home/valgrind/users.html #1.69:1.70 @@ -418,6 +418,6 @@ <dd>An eBay auction listing tracker. -<dt><a href="http://www.worldforge.com/">Worldforge</a> -<dd>A web search engine and portal. +<dt><a href="http://www.worldforge.org/">Worldforge</a> +<dd>An engine for online roleplaying games. </dl> |
|
From: Nicholas N. <nj...@ca...> - 2004-07-07 23:19:45
|
CVS commit by nethercote:
Concentrate, Nick, concentrate.
M +3 -3 users.html 1.71
--- devel-home/valgrind/users.html #1.70:1.71
@@ -384,4 +384,7 @@
<dd>A high performance cross-platform game engine for Windows, Linux,
PS2 and XBox. Free for non-console development.
+
+<dt><a href="http://www.worldforge.org/">Worldforge</a>
+<dd>An engine for online roleplaying games.
</dl>
@@ -417,7 +420,4 @@
<dt><a href="http://bidwatcher.sf.net/">Bidwatcher</a>
<dd>An eBay auction listing tracker.
-
-<dt><a href="http://www.worldforge.org/">Worldforge</a>
-<dd>An engine for online roleplaying games.
</dl>
|
|
From: Nicholas N. <nj...@ca...> - 2004-07-08 08:46:29
|
CVS commit by nethercote: Added Zori. M +3 -0 users.html 1.72 --- devel-home/valgrind/users.html #1.71:1.72 @@ -145,4 +145,7 @@ <dt><a href="http://www.parl.clemson.edu/~wjones/research/index.html">Beosim</a> <dd>A Beowulf grid simulator. + +<dt><a href="http://zori.aspuru.com">Zori</a> +<dd>A GPL quantum Monte Carlo (QMC) program. </dl> |
|
From: Nicholas N. <nj...@ca...> - 2004-07-18 10:37:48
|
CVS commit by nethercote: Duplicate changes just committed to main FAQ.txt. Does anyone know how to create this faq.html by pulling in the contents of FAQ.txt from CVS? M +7 -2 faq.html 1.5 --- devel-home/valgrind/faq.html #1.4:1.5 @@ -10,5 +10,5 @@ Valgrind FAQ, version 2.1.2 ~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Last revised 6 April 2004 +Last revised 18 July 2004 ~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -127,7 +127,12 @@ instructions. If it still happens with newer versions, if the failing instruction is an SSE/SSE2 instruction, you might be able to recompile -your progrma without it by using the flag -march to gcc. Either way, +your program without it by using the flag -march to gcc. Either way, let us know and we'll try to fix it. +Another possibility is that your program has a bug and erroneously jumps +to a non-code address, in which case you'll get a SIGILL signal. +Memcheck/Addrcheck may issue a warning just before this happens, but they +might not if the jump happens to land in addressable memory. + ----------------------------------------------------------------- |
|
From: Julian S. <js...@ac...> - 2004-07-18 10:52:37
|
CVS commit by jseward: Update for Valgrind-2.1.2 release. M +4 -0 bugs.html 1.12 M +3 -3 docs.html 1.8 M +26 -49 downloads.html 1.13 M +3 -2 index.html 1.22 M +7 -2 news.html 1.6 M +2 -1 tools.html 1.8 --- devel-home/valgrind/bugs.html #1.11:1.12 @@ -32,4 +32,8 @@ <p> +Filing bug reports in bugzilla is the most effective way of getting +the developers to look at it. Mailing the developers individually +your <em>least effective</em> solution. Please use bugzilla! + <?php include "footer.inc" --- devel-home/valgrind/docs.html #1.7:1.8 @@ -5,7 +5,7 @@ ?> -<a href="http://developer.kde.org/~sewardj/docs-2.0.0/manual.html">Full -documentation</a> for version 2.0.0 is supplied, up-to-date as of 11 November -2003. +<a href="http://developer.kde.org/~sewardj/docs-2.1.2/manual.html">Full +documentation</a> for version 2.1.2 is supplied, up-to-date as of 18 +July 2004. <p> The following tutorials may be slightly out-of-date, but should give a good --- devel-home/valgrind/downloads.html #1.12:1.13 @@ -25,62 +25,39 @@ -<h3>Older Stable Releases</h3> - -None available. - <h3>Current Development Release</h3> -<strong>2.1.1 (of 12 March 2004)</strong> - <a HREF="http://developer.kde.org/~sewardj/valgrind-2.1.1.tar.bz2">(bzip2'd source, 923KB)</a> - (MD5=0010c3e8f054ecc633151c62044b646d) -<p> -2.1.1 contains some internal structural changes needed for V's -long-term future. These don't affect end-users. There are -also some useful user-visible changes. -<ul> -<li> -Greater isolation between Valgrind and the program being run, so - the program is less likely to inadvertently kill Valgrind by - doing wild writes. -<p><li> -Massif: a new space profiling tool. Try it! It's cool, and it'll - tell you in detail where and when your C/C++ code is allocating heap. - Draws pretty .ps pictures of memory use against time. A potentially - powerful tool for making sense of your program's space use. -<p><li> -Fixes for many bugs, including support for more SSE2/SSE3 instructions, - various signal/syscall things, and various problems with debug - info readers. -<p><li> -Support for glibc-2.3.3 based systems. -</ul> - -We are now doing automatic overnight build-and-test runs on a variety -of distros. As a result, we believe 2.1.1 builds and runs on: -Red Hat 7.2, 7.3, 8.0, 9, Fedora Core 1, SuSE 8.2, SuSE 9. - - +<strong>2.1.2 (of 18 July 2004)</strong> + <a HREF="http://developer.kde.org/~sewardj/valgrind-2.1.2.tar.bz2">(bzip2'd source, 961KB)</a> + (MD5=646d42f7e2be4745842e2ff76b62fbc0) +<p> +2.1.2 contains four months worth of bug fixes and refinements. +Although officially a developer release, we believe it to be stable +enough for widespread day-to-day use. 2.1.2 is pretty good, so try it +first, although there is a chance it won't work. If so then try 2.0.0 +and tell us what went wrong. 2.1.2 fixes a lot of problems present +in 2.0.0 and is generally a much better product. +<p> +Relative to 2.1.1, a large number of minor problems have +been fixed, and so if you use 2.1.1 you should try 2.1.2. Users of +the last stable release, 2.0.0, might also want to try this release. +For one thing, 2.1.2 compiles with gcc-3.4.X, whereas 2.0.0 doesn't. +<p> +The +<a HREF="http://developer.kde.org/~sewardj/docs-2.1.2/NEWS.txt">NEWS</a> +file in the distro contains a detailed list of bug fixes and changes. -<h3>Older Development Release</h3> +<p> +The 2.1.2 documentation is available on-line +<a href="http://developer.kde.org/~sewardj/docs-2.1.2/manual.html">here +</a>. -<strong>2.1.0 (of 14 December 2003)</strong> - <a HREF="http://developer.kde.org/~sewardj/valgrind-2.1.0.tar.bz2">(bzip2'd source, 762KB)</a> - (MD5=3e4056dd45163a5f555a23ced2f95191) <p> -2.1.0 brings an overhaul of syscall and signal handling, giving much -better behaviour, especially in threaded code. 2.1.0 can also check -for file descriptor leakage. A few more SSE/SSE2 instructions are -implemented, and various reported bugs have been fixed. See the <a -HREF="http://developer.kde.org/~sewardj/docs-2.1.0/NEWS.txt">NEWS</a> -file in the distro for more details. -<p> -2.1.0 is known to compile and work on: SuSE 9, SuSE 8.2, RedHat 8, -RedHat 7.3, Debian Sid. Probably works on RedHat 9, although we -haven't had explicit confirmation of that yet. - +We are now doing automatic overnight build-and-test runs on a variety +of distros. As a result, we believe 2.1.2 builds and runs on: +Red Hat 7.2, 7.3, 8.0, 9, Fedora Core 2, SuSE 9.1. --- devel-home/valgrind/index.html #1.21:1.22 @@ -5,6 +5,7 @@ ?> -<p class="news">March 12, 2004: A new unstable release, -<a href="downloads.html">valgrind 2.1.1</a>, is available. +<p class="news">July 18, 2004: A new developer release, +<a href="downloads.html">valgrind 2.1.2</a>, is available. 2.1.2 + fixes many bugs in 2.1.1, and includes the new Massif heap-profiling tool. <p class="news">March 04, 2004: An experimental PowerPC port is available. --- devel-home/valgrind/news.html #1.5:1.6 @@ -5,5 +5,10 @@ ?> -<p class="news">March 12, 2004: A new unstable release, +<p class="news">July 18, 2004: A new developer release, +<a href="downloads.html">valgrind 2.1.2</a>, is available. + 2.1.2 fixes many bugs in 2.1.1, and includes the new Massif + heap-profiling tool. + +<p class="news">March 12, 2004: A new developer release, <a href="downloads.html">valgrind 2.1.1</a>, is available. @@ -21,5 +26,5 @@ (<a href="http://builder.com.com/5100-6375-5136747.html">interview</a>). -<p class="news">December 14, 2003: A new unstable release, +<p class="news">December 14, 2003: A new developer release, <a href="downloads.html">valgrind 2.1.0</a>, is available. --- devel-home/valgrind/tools.html #1.7:1.8 @@ -65,5 +65,6 @@ allocated. Massif runs programs about 20x slower than normal. Massif was introduced in version 2.1.1 of Valgrind. - + <p> + <li><strong>Helgrind</strong> is a thread debugger which finds data races in multithreaded programs. It looks for memory locations which are |
|
From: Julian S. <js...@ac...> - 2004-07-18 11:07:36
|
CVS commit by jseward: Promoting the idea that we can't count accurately up to five is probably not good :-) M +1 -1 tools.html 1.9 --- devel-home/valgrind/tools.html #1.8:1.9 @@ -5,5 +5,5 @@ ?> -The Valgrind distribution includes four useful debugging and profiling tools. +The Valgrind distribution includes five useful debugging and profiling tools. <ul> |
|
From: Julian S. <js...@ac...> - 2004-07-18 11:07:59
|
CVS commit by jseward:
This was getting a bit old.
M +11 -12 sysreqs.html 1.7
--- devel-home/valgrind/sysreqs.html #1.6:1.7
@@ -14,26 +14,25 @@
<h3>Operating System</h3>
You must be running Linux kernel 2.4.X, 2.5.X or 2.6.X, and glibc 2.2.X or
-2.3.X. That covers the vast majority of installed systems at present. Ancient
-systems (glibc-2.1.3, Red Hat 6.2 for example) might still work with some
-effort (they once used to), but don't bet on it.
+2.3.X. That covers the vast majority of installed systems at present.
+The oldest system we test on is Red Hat 7.2, which is getting pretty
+long in the tooth by now.
<p>
-The 2.0.0 stable release is known to build and run on Red Hats 7.3,
-8, 9, SuSE 8.0 and SuSE 8.2. Chances are good that it will build and
+The 2.1.2 stable release is known to build and run on Red Hats 7.2,
+7.3, 8, 9, Fedora Core 2 and SuSE 9.1. It should work on both NPTL and
+PosixThreads based systems. Chances are good that it will build and
work for you if you have any non-ancient Linux distribution.
<p>
+The 2.0.0 stable release is known to build and run on Red Hats 7.3,
+8, 9, SuSE 8.0 and SuSE 8.2.
+<p>
<h3>Limitations</h3>
-There are some, the most significant of which are:
+There are some, the most significant of which is:
<ul>
-<li>Incomplete support for SIMD instructions. 2.0.0 has complete
- MMX support, and pretty good SSE/SSE2 support, but some instructions
- are still not handled. 3DNow! (rapidly becoming 3DThen!) is not
- supported at all.
- <p>
<li>Support for non-POSIX signal stuff is flaky. If you stick to POSIX
signals you should be ok.
<p>
</ul>
-<a href="http://developer.kde.org/~sewardj/docs-2.0.0/coregrind_core.html#limits">
+<a href="http://developer.kde.org/~sewardj/docs-2.1.2/coregrind_core.html#limits">
Section 2.12 of the manual</a> contains a complete list of limitations.
<p>
|
|
From: Nicholas N. <nj...@ca...> - 2004-07-18 11:30:35
|
CVS commit by nethercote: Removed some older news items from the front page (still viewable in the news.html page). M +0 -6 index.html 1.23 --- devel-home/valgrind/index.html #1.22:1.23 @@ -11,10 +11,4 @@ <p class="news">March 04, 2004: An experimental PowerPC port is available. See <a href="related.html">Related Projects</a>. - -<p class="news">February 15, 2004: Valgrind CVS now includes Massif, a heap -profiling tool. - -<p class="news">January 27, 2004: We have a new page listing -<a href="users.html">projects using Valgrind</a>. <hr> |
|
From: Julian S. <js...@ac...> - 2004-07-18 11:34:44
|
CVS commit by jseward: Update the MD5 for 2.1.2. M +2 -2 downloads.html 1.14 --- devel-home/valgrind/downloads.html #1.13:1.14 @@ -29,6 +29,6 @@ <strong>2.1.2 (of 18 July 2004)</strong> - <a HREF="http://developer.kde.org/~sewardj/valgrind-2.1.2.tar.bz2">(bzip2'd source, 961KB)</a> - (MD5=646d42f7e2be4745842e2ff76b62fbc0) + <a HREF="http://developer.kde.org/~sewardj/valgrind-2.1.2.tar.bz2">(bzip2'd source, 962KB)</a> + (MD5=585e3ac5f7b86d6cd3e2bed07af732de) <p> 2.1.2 contains four months worth of bug fixes and refinements. |
|
From: Nicholas N. <nj...@ca...> - 2004-07-20 11:32:26
|
CVS commit by nethercote:
Update
M +4 -4 related.html 1.16
--- devel-home/valgrind/related.html #1.15:1.16
@@ -26,8 +26,8 @@
can profile shared libraries.
<p>
-<li>Nick Nethercote has three experimental tools: a heap profiler, a
- pointer misuse-checker, and a signal-handler checker. He also has
- an experimental Valgrind distribution that has an interactive command
- line. They are all available
+<li>Nick Nethercote has three experimental tools: a memory access tracer, a
+ heap profiler, a pointer misuse-checker, and a signal-handler checker. He
+ also has an experimental Valgrind distribution that has an interactive
+ command line. They are all available
<a href="http://www.cl.cam.ac.uk/~njn25/valgrind.html">here</a>.
<p>
|
|
From: Nicholas N. <nj...@ca...> - 2004-07-20 11:34:15
|
CVS commit by nethercote: Clarify bug-submission procedure. M +32 -19 bugs.html 1.13 --- devel-home/valgrind/bugs.html #1.12:1.13 @@ -5,19 +5,36 @@ ?> -Before you report a bug, please consult the -<a HREF="faq.html">Frequently Asked Questions</a>. It -contains workarounds for more or less all the failure conditions for -which we know a workaround. This includes a large fraction of the -failures people seem to encounter in practice. -<p> -If that fails, please file a report using our -<a href="http://bugs.kde.org/enter_valgrind_bug.cgi">Bugzilla page</a>. -Patches for bugs are particularly welcome. -<p> -If you have trouble with Bugzilla, or for some reason you don't think -Bugzilla is appropriate for your report (although it probably is), -contact the valgrind-users <a href="lists.html">mailing list</a>. We -try to respond to most bug reports, but if we don't, it doesn't mean we -are ignoring you; it may well be that the bug has been reported before. +If you think you've found a Valgrind bug, please take the following steps. +<ul> +<li>Before you report a bug, please consult the + <a HREF="faq.html">Frequently Asked Questions</a>. It contains + more or less all the failure conditions for which we know a + workaround. This includes a large fraction of the failures people + seem to encounter in practice. + <p> + +<li>If that fails, please file a report using our + <a href="http://bugs.kde.org/enter_valgrind_bug.cgi">Bugzilla page</a>. + Please check if the bug has already been reported. Patches for bugs + are particularly welcome. All Bugzilla reports are read by the + developers. If you get no response, we are not ignoring the bug; + we probably just don't know how to fix it satisfactorily yet. Some + bugs are fixed immediately, some take months, but if they are in + Bugzilla, they won't be forgotten, and other people can search for + them. + <p> + +<li>If you are not sure if what you are seeing is actually a bug, you + could contact the valgrind-users <a href="lists.html">mailing + list</a>. The developers all read the list, but there is no + guarantee you will get a useful response. Often we will ask you to + put the problem into Bugzilla anyway. + <p> + +<li>Please do not email developers individually; this is the + <em>least effective</em> way of getting a bug fixed. + <p> +</ul> + <p> When you report a bug, <em>please</em> give the following information: @@ -32,8 +49,4 @@ <p> -Filing bug reports in bugzilla is the most effective way of getting -the developers to look at it. Mailing the developers individually -your <em>least effective</em> solution. Please use bugzilla! - <?php include "footer.inc" |