Author: breser
Date: Thu Apr 4 01:35:58 2013
New Revision: 1464253
URL: http://svn.apache.org/r1464253
Log:
* publish/faq.html
(dynamic-exe-debugging): Provide a much easier method for debugging dynamic
libraries in the build tree.
Modified:
subversion/site/publish/faq.html
Modified: subversion/site/publish/faq.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/faq.html?rev=1464253&r1=1464252&r2=1464253&view=diff
==============================================================================
--- subversion/site/publish/faq.html (original)
+++ subversion/site/publish/faq.html Thu Apr 4 01:35:58 2013
@@ -4330,20 +4330,17 @@ real binary. As shown below, this compl
executable format: File format not recognized</code></div>
</blockquote>
-<p>While this can be worked around by building using the
-<code>--disable-shared</code> argument to configure to statically link
-the binaries, or installing them and pointing your debugger at the
-installed version, it's often necessary or more expedient to be able
-to debug them right within your source tree.</p>
-
-<p>To do so, edit the last <code>exec</code> statement in the shell
-script to run the real binary in your debugger. With gdb, this
-amounts to replacing <code>exec "$progdir/$progname"</code> with
-<code>exec gdb --args "$progdir/$progname"</code>.</p>
-
-<p>This trick is also very useful when applied to the
-libtool-generated shell scripts for the white box tests.</p>
+<p>You can work around this by running gdb via the libtool command.
+The libtool command in execute mode will detect that the svn command is a
+libtool wrapper script and handle setting the appropriate environment
+variables and replace the script with the path to the real file before
+running gdb..
+</p>
+<p>Your command line would look something like this:</p>
+<blockquote>
+<div><code>$ libtool execute gdb subversion/svn/svn</code></div>
+</blockquote>
</div>
