From 88e337b56877441e59c0322aed126e4a4d79b5e9 Mon Sep 17 00:00:00 2001
From: Nicholas Nethercote <n.nethercote@gmail.com>
Date: Thu, 18 Nov 2004 18:35:02 +0000
Subject: [PATCH] Fix incorrect info about using GDB on Valgrind.

MERGED FROM HEAD


git-svn-id: svn://svn.valgrind.org/valgrind/branches/VALGRIND_2_2_0_BRANCH@3047
---
 coregrind/docs/coregrind_tools.html | 29 ++---------------------------
 1 file changed, 2 insertions(+), 27 deletions(-)

diff --git a/coregrind/docs/coregrind_tools.html b/coregrind/docs/coregrind_tools.html
index 7fc0b5381c..19f79733b9 100644
--- a/coregrind/docs/coregrind_tools.html
+++ b/coregrind/docs/coregrind_tools.html
@@ -547,33 +547,8 @@ usual GDB command:
 usually gives the location of the segmentation fault.<p>
 
 If you want to debug C functions used by your tool, you can attach GDB to
-Valgrind with some effort:
-<ul>
-  <li>Enable the following code in <code>coregrind/vg_main.c</code> by
-  changing <code>if (0)</code> into <code>if (1)</code>:
-<pre>
-   /* Hook to delay things long enough so we can get the pid and
-      attach GDB in another shell. */
-   if (0) { 
-      Int p, q;
-      for (p = 0; p < 50000; p++)
-         for (q = 0; q < 50000; q++) ;
-   }
-</pre>
-      </li><p>
-      and rebuild Valgrind.
-
-  <li>Then run: 
-      <blockquote><code>valgrind <i>prog</i></code></blockquote>
-
-      Valgrind starts the program, printing its process id, and then delays for
-      a few seconds (you may have to change the loop bounds to get a suitable
-      delay).</li><p>
-      
-  <li>In a second shell run: 
-  
-      <blockquote><code>gdb <i>prog</i> <i>pid</i></code></blockquote></li><p>
-</ul>
+Valgrind with some effort; see the file <code>README_DEVELOPERS</code> in
+CVS for instructions.<p>
 
 GDB may be able to give you useful information.  Note that by default
 most of the system is built with <code>-fomit-frame-pointer</code>,
-- 
2.47.2