make syntax-check
make -C tests valgrind
-
-
- Valgrind
- http://valgrind.org/is a test that checks for memory management issues, such as leaks or use of
-uninitialized variables.
+Valgrind <http://valgrind.org/> is a test that checks for memory management
+issues, such as leaks or use of uninitialized variables.
If you encounter any failing tests, the VIR_TEST_DEBUG environment variable
may provide extra information to debug the failures. Larger values of
in order to add a suppression filter. The filter should be unique enough to
not suppress real leaks, but it should be generic enough to cover multiple
code paths. The format of the entry can be found in the documentation found at
-the
-
- Valgrind home page.
- http://valgrind.org/The following trace was added to "tests/.valgrind.supp" in order to suppress
-the warning:
+the Valgrind home page <http://valgrind.org/>. The following trace was added
+to "tests/.valgrind.supp" in order to suppress the warning:
{
dlInitMemoryLeak1
There is more on this subject, including lots of links to background reading
-on the subject, on
-
- Richard Jones' guide to working with open source projects
- http://et.redhat.com/~rjones/how-to-supply-code-to-open-source-projects/
+on the subject, on Richard Jones' guide to working with open source projects
+<http://et.redhat.com/~rjones/how-to-supply-code-to-open-source-projects/>.
Code indentation
Although libvirt does not encourage the Linux kernel wind/unwind style of
multiple labels, there's a good general discussion of the issue archived at
-
- KernelTrap
- http://kerneltrap.org/node/553/2131
+KernelTrap <http://kerneltrap.org/node/553/2131>
When using goto, please use one of these standard labels if it makes sense:
not suppress real leaks, but it should be generic enough to
cover multiple code paths. The format of the entry can be
found in the documentation found at the
- <a href="http://valgrind.org/">Valgrind home page.</a>
+ <a href="http://valgrind.org/">Valgrind home page</a>.
The following trace was added to <code>tests/.valgrind.supp</code>
in order to suppress the warning:
</p>
There is more on this subject, including lots of links to background
reading on the subject, on
<a href="http://et.redhat.com/~rjones/how-to-supply-code-to-open-source-projects/">
- Richard Jones' guide to working with open source projects</a>
+ Richard Jones' guide to working with open source projects</a>.
</p>
<xsl:template match="html:i">'<xsl:apply-templates/>'</xsl:template>
<xsl:template match="html:code">"<xsl:apply-templates/>"</xsl:template>
+<!-- likewise, reformat a tags in first pass -->
+<xsl:template match="html:a">
+<xsl:text> </xsl:text><xsl:apply-templates/>
+<xsl:if test="@href">
+ <xsl:text> <</xsl:text><xsl:value-of select="@href"/>
+ <xsl:text>></xsl:text>
+</xsl:if>
+</xsl:template>
+
+
</xsl:stylesheet>
</xsl:template>
-
-<xsl:template match="html:a">
-<xsl:value-of select="$newline"/><xsl:value-of select="$newline"/>
-<xsl:text> </xsl:text><xsl:apply-templates/>
-<xsl:value-of select="$newline"/>
-<xsl:text> </xsl:text><xsl:value-of select="@href"/>
-</xsl:template>
-
</xsl:stylesheet>