From: Misha Brukman <brukman+llvm@gmail.com>
Date: Wed, 12 May 2004 00:57:24 +0000 (+0000)
Subject: Add link to Valgrind.
X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=300e74b43fd75d240bea59049c3b729e3b0d9539;p=oota-llvm.git

Add link to Valgrind.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@13472 91177308-0d34-0410-b5e6-96231b3b80d8
---

diff --git a/docs/HowToSubmitABug.html b/docs/HowToSubmitABug.html
index 16e4c24a58b..69da4fafdbf 100644
--- a/docs/HowToSubmitABug.html
+++ b/docs/HowToSubmitABug.html
@@ -231,8 +231,9 @@ before defining them, etc.) which the verifier will check for after a pass
 finishes its run.</p>
 
 <p>If it looks like the LLVM compiler is miscompiling a program, the very first
-thing to check is to make sure it is not using undefined behavior.  In 
-particular, check to see if the program valgrinds clean, passes purify, or some
+thing to check is to make sure it is not using undefined behavior.  In
+particular, check to see if the program <a
+href="http://valgrind.kde.org/">valgrind</a>s clean, passes purify, or some
 other memory checker tool.  Many of the "LLVM bugs" that we have chased down
 ended up being bugs in the program being compiled, not LLVM.</p>