mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-04 10:21:20 +00:00
b05a2a18d7
following improvements: - Arch/OS/platform-specific files are now included/excluded via the preprocessor, rather than via the build system. This is more consistent (we use the pre-processor for small arch/OS/platform-specific chunks within files) and makes the build system much simpler, as the sources for all programs are the same on all platforms. - Vast amounts of cut+paste Makefile.am code has been factored out. If a new platform is implemented, you need to add 11 extra Makefile.am lines. Previously it was over 100 lines. - Vex has been autotoolised. Dependency checking now works in Vex (no more incomplete builds). Parallel builds now also work. --with-vex no longer works; it's little use and a pain to support. VEX/Makefile is still in the Vex repository and gets overwritten at configure-time; it should probably be renamed Makefile-gcc to avoid possible problems, such as accidentally committing a generated Makefile. There's a bunch of hacky copying to deal with the fact that autotools don't handle same-named files in different directories. Julian plans to rename the files to avoid this problem. - Various small Makefile.am things have been made more standard automake style, eg. the use of pkginclude/pkglib prefixes instead of rolling our own. - The existing five top-level Makefile.am include files have been consolidated into three. - Most Makefile.am files now are structured more clearly, with comment headers separating sections, declarations relating to the same things next to each other, better spacing and layout, etc. - Removed the unused exp-ptrcheck/tests/x86 directory. - Renamed some XML files. - Factored out some duplicated dSYM handling code. - Split auxprogs/ into auxprogs/ and mpi/, which allowed the resulting Makefile.am files to be much more standard. - Cleaned up m_coredump by merging a bunch of files that had been overzealously separated. The net result is 630 fewer lines of Makefile.am code, or 897 if you exclude the added Makefile.vex.am, or 997 once the hacky file copying for Vex is removed. And the build system is much simpler. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10364
65 lines
2.5 KiB
XML
65 lines
2.5 KiB
XML
<?xml version="1.0"?> <!-- -*- sgml -*- -->
|
|
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
|
|
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
|
|
|
|
|
|
<chapter id="design-impl"
|
|
xreflabel="The design and implementation of Valgrind">
|
|
|
|
<title>The Design and Implementation of Valgrind</title>
|
|
|
|
|
|
<para>A number of academic publications nicely describe many aspects
|
|
of Valgrind's design and implementation. Online copies of all of
|
|
them, and others, are available at
|
|
http://valgrind.org/docs/pubs.html.</para>
|
|
|
|
<para>A good top-level overview of Valgrind is given in:</para>
|
|
|
|
<para>
|
|
"Valgrind: A Framework for Heavyweight Dynamic Binary
|
|
Instrumentation." Nicholas Nethercote and Julian Seward. Proceedings
|
|
of ACM SIGPLAN 2007 Conference on Programming Language Design and
|
|
Implementation (PLDI 2007), San Diego, California, USA, June 2007.
|
|
This paper describes how Valgrind works, and how it differs from other
|
|
DBI frameworks such as Pin and DynamoRIO.</para>
|
|
|
|
|
|
<para>The following two papers together give a comprehensive
|
|
description of how Memcheck works:</para>
|
|
|
|
<para>"Using Valgrind to detect undefined value errors with
|
|
bit-precision." Julian Seward and Nicholas Nethercote. Proceedings
|
|
of the USENIX'05 Annual Technical Conference, Anaheim, California,
|
|
USA, April 2005. This paper describes in detail how Memcheck's
|
|
undefined value error detection (a.k.a. V bits) works.</para>
|
|
|
|
<para>"How to Shadow Every Byte of Memory Used by a Program."
|
|
Nicholas Nethercote and Julian Seward. Proceedings of the Third
|
|
International ACM SIGPLAN/SIGOPS Conference on Virtual Execution
|
|
Environments (VEE 2007), San Diego, California, USA, June 2007. This
|
|
paper describes in detail how Memcheck's shadow memory is implemented,
|
|
and compares it to other alternative approaches.</para>
|
|
|
|
|
|
<para>The following paper describes Callgrind:</para>
|
|
|
|
<para>"A Tool Suite for Simulation Based Analysis of Memory Access
|
|
Behavior." Josef Weidendorfer, Markus Kowarschik and Carsten
|
|
Trinitis. Proceedings of the 4th International Conference on
|
|
Computational Science (ICCS 2004), Krakow, Poland, June 2004. This
|
|
paper describes Callgrind.</para>
|
|
|
|
<para>The following dissertation describes Valgrind in some detail
|
|
(some of these details are now out-of-date) as well as Cachegrind,
|
|
Annelid and Redux. It also covers some underlying theory about
|
|
dynamic binary analysis in general and what all these tools have in
|
|
common:</para>
|
|
|
|
<para>"Dynamic Binary Analysis and Instrumentation." Nicholas
|
|
Nethercote. PhD Dissertation, University of Cambridge, November
|
|
2004.</para>
|
|
|
|
|
|
</chapter>
|