|
From: <sv...@va...> - 2011-11-24 17:12:50
|
Author: florian
Date: 2011-11-24 17:08:09 +0000 (Thu, 24 Nov 2011)
New Revision: 444
Log:
Fix anchor tags after file rename.
Modified:
trunk/docs/manual/sg-manual.html
Modified: trunk/docs/manual/sg-manual.html
===================================================================
--- trunk/docs/manual/sg-manual.html 2011-11-24 17:05:34 UTC (rev 443)
+++ trunk/docs/manual/sg-manual.html 2011-11-24 17:08:09 UTC (rev 444)
@@ -19,18 +19,18 @@
</tr></table></div>
<div class="chapter" title="11.SGCheck: an experimental heap, stack and global array overrun detector">
<div class="titlepage"><div><div><h2 class="title">
-<a name="pc-manual"></a>11.SGCheck: an experimental heap, stack and global array overrun detector</h2></div></div></div>
+<a name="sg-manual"></a>11.SGCheck: an experimental heap, stack and global array overrun detector</h2></div></div></div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
-<dt><span class="sect1"><a href="pc-manual.html#pc-manual.overview">11.1. Overview</a></span></dt>
-<dt><span class="sect1"><a href="pc-manual.html#pc-manual.options">11.2. SGCheck Command-line Options</a></span></dt>
-<dt><span class="sect1"><a href="pc-manual.html#pc-manual.how-works.heap-checks">11.3. How SGCheck Works: Heap Checks</a></span></dt>
-<dt><span class="sect1"><a href="pc-manual.html#pc-manual.how-works.sg-checks">11.4. How SGCheck Works: Stack and Global Checks</a></span></dt>
-<dt><span class="sect1"><a href="pc-manual.html#pc-manual.cmp-w-memcheck">11.5. Comparison with Memcheck</a></span></dt>
-<dt><span class="sect1"><a href="pc-manual.html#pc-manual.limitations">11.6. Limitations</a></span></dt>
-<dt><span class="sect1"><a href="pc-manual.html#pc-manual.todo-user-visible">11.7. Still To Do: User-visible Functionality</a></span></dt>
-<dt><span class="sect1"><a href="pc-manual.html#pc-manual.todo-implementation">11.8. Still To Do: Implementation Tidying</a></span></dt>
+<dt><span class="sect1"><a href="sg-manual.html#sg-manual.overview">11.1. Overview</a></span></dt>
+<dt><span class="sect1"><a href="sg-manual.html#sg-manual.options">11.2. SGCheck Command-line Options</a></span></dt>
+<dt><span class="sect1"><a href="sg-manual.html#sg-manual.how-works.heap-checks">11.3. How SGCheck Works: Heap Checks</a></span></dt>
+<dt><span class="sect1"><a href="sg-manual.html#sg-manual.how-works.sg-checks">11.4. How SGCheck Works: Stack and Global Checks</a></span></dt>
+<dt><span class="sect1"><a href="sg-manual.html#sg-manual.cmp-w-memcheck">11.5. Comparison with Memcheck</a></span></dt>
+<dt><span class="sect1"><a href="sg-manual.html#sg-manual.limitations">11.6. Limitations</a></span></dt>
+<dt><span class="sect1"><a href="sg-manual.html#sg-manual.todo-user-visible">11.7. Still To Do: User-visible Functionality</a></span></dt>
+<dt><span class="sect1"><a href="sg-manual.html#sg-manual.todo-implementation">11.8. Still To Do: Implementation Tidying</a></span></dt>
</dl>
</div>
<p>To use this tool, you must specify
@@ -38,7 +38,7 @@
command line.</p>
<div class="sect1" title="11.1.Overview">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="pc-manual.overview"></a>11.1.Overview</h2></div></div></div>
+<a name="sg-manual.overview"></a>11.1.Overview</h2></div></div></div>
<p>SGCheck is a tool for finding overruns of heap, stack
and global arrays. Its functionality overlaps somewhat with
Memcheck's, but it is able to catch invalid accesses in a number of
@@ -62,7 +62,7 @@
</div>
<div class="sect1" title="11.2.SGCheck Command-line Options">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="pc-manual.options"></a>11.2.SGCheck Command-line Options</h2></div></div></div>
+<a name="sg-manual.options"></a>11.2.SGCheck Command-line Options</h2></div></div></div>
<p>SGCheck-specific command-line options are:</p>
<div class="variablelist">
<a name="pc.opts.list"></a><dl>
@@ -107,7 +107,7 @@
</div>
<div class="sect1" title="11.3.How SGCheck Works: Heap Checks">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="pc-manual.how-works.heap-checks"></a>11.3.How SGCheck Works: Heap Checks</h2></div></div></div>
+<a name="sg-manual.how-works.heap-checks"></a>11.3.How SGCheck Works: Heap Checks</h2></div></div></div>
<p>SGCheck can check for invalid uses of heap pointers, including
out of range accesses and accesses to freed memory. The mechanism is
however completely different from Memcheck's, and the checking is more
@@ -133,7 +133,7 @@
</div>
<div class="sect1" title="11.4.How SGCheck Works: Stack and Global Checks">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="pc-manual.how-works.sg-checks"></a>11.4.How SGCheck Works: Stack and Global Checks</h2></div></div></div>
+<a name="sg-manual.how-works.sg-checks"></a>11.4.How SGCheck Works: Stack and Global Checks</h2></div></div></div>
<p>When a source file is compiled
with <code class="option">-g</code>, the compiler attaches DWARF3
debugging information which describes the location of all stack and
@@ -182,7 +182,7 @@
</div>
<div class="sect1" title="11.5.Comparison with Memcheck">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="pc-manual.cmp-w-memcheck"></a>11.5.Comparison with Memcheck</h2></div></div></div>
+<a name="sg-manual.cmp-w-memcheck"></a>11.5.Comparison with Memcheck</h2></div></div></div>
<p>Memcheck does not do any access checks for stack or global arrays, so
the presence of those in SGCheck is a straight win. (But see
"Limitations" below).</p>
@@ -241,7 +241,7 @@
</div>
<div class="sect1" title="11.6.Limitations">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="pc-manual.limitations"></a>11.6.Limitations</h2></div></div></div>
+<a name="sg-manual.limitations"></a>11.6.Limitations</h2></div></div></div>
<p>This is an experimental tool, which relies rather too heavily on some
not-as-robust-as-I-would-like assumptions on the behaviour of correct
programs. There are a number of limitations which you should be aware
@@ -262,7 +262,7 @@
calls are handled. If an unhandled one is encountered, SGCheck will
abort. Fortunately, adding support for a new syscall is very
easy.</p></li>
-<li class="listitem"><p>Stack checks: It follows from the description above (<a class="xref" href="pc-manual.html#pc-manual.how-works.sg-checks" title="11.4.How SGCheck Works: Stack and Global Checks">How SGCheck Works: Stack and Global Checks</a>) that the first access by a
+<li class="listitem"><p>Stack checks: It follows from the description above (<a class="xref" href="sg-manual.html#sg-manual.how-works.sg-checks" title="11.4.How SGCheck Works: Stack and Global Checks">How SGCheck Works: Stack and Global Checks</a>) that the first access by a
memory referencing instruction to a stack or global array creates an
association between that instruction and the array, which is checked on
subsequent accesses by that instruction, until the containing function
@@ -349,7 +349,7 @@
</div>
<div class="sect1" title="11.7.Still To Do: User-visible Functionality">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="pc-manual.todo-user-visible"></a>11.7.Still To Do: User-visible Functionality</h2></div></div></div>
+<a name="sg-manual.todo-user-visible"></a>11.7.Still To Do: User-visible Functionality</h2></div></div></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem"><p>Extend system call checking to work on stack and global arrays.</p></li>
<li class="listitem"><p>Print a warning if a shared object does not have debug info
@@ -359,7 +359,7 @@
</div>
<div class="sect1" title="11.8.Still To Do: Implementation Tidying">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="pc-manual.todo-implementation"></a>11.8.Still To Do: Implementation Tidying</h2></div></div></div>
+<a name="sg-manual.todo-implementation"></a>11.8.Still To Do: Implementation Tidying</h2></div></div></div>
<p>Items marked CRITICAL are considered important for correctness:
non-fixage of them is liable to lead to crashes or assertion failures
in real use.</p>
|