Documentation update for 3.6.0 (not including NEWS).
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11440 a5019735-40e9-0310-863c-91ae7b9d1cf9
diff --git a/AUTHORS b/AUTHORS
index dbfd904..de0c9c7 100644
--- a/AUTHORS
+++ b/AUTHORS
@@ -1,7 +1,8 @@
-Julian Seward was the original founder, designer and author of Valgrind,
-created the dynamic translation frameworks, wrote Memcheck and 3.3.X
-Helgrind, and did lots of other things.
+Julian Seward was the original founder, designer and author of
+Valgrind, created the dynamic translation frameworks, wrote Memcheck,
+the 3.X versions of Helgrind, Ptrcheck, DHAT, and did lots of other
+things.
Nicholas Nethercote did the core/tool generalisation, wrote
Cachegrind and Massif, and tons of other stuff.
@@ -33,8 +34,12 @@
Bart Van Assche wrote and maintains DRD.
-Cerion Armour-Brown worked on PowerPC instruction set support in
-the Vex dynamic-translation framework.
+Cerion Armour-Brown worked on PowerPC instruction set support in the
+Vex dynamic-translation framework. Maynard Johnson improved the
+Power6 support.
+
+Kirill Batuzov and Dmitry Zhurikhin did the NEON instruction set
+support for ARM. Donna Robinson did the v6 media instruction support.
Donna Robinson created and maintains the very excellent
http://www.valgrind.org.
diff --git a/NEWS b/NEWS
index dd3dc21..4682c37 100644
--- a/NEWS
+++ b/NEWS
@@ -13,6 +13,8 @@
Matching Valkyrie support (for Mc, Hg, Pc)
Hg annotation improvements
More reliable stack unwinding on amd64-linux
+Callgrind branch prediction and global bus
+Segfaults .w.r.t boost
Punted but under consideration for 3.7:
Support for code compiled by LLVM-2.8
diff --git a/README b/README
index 71c525f..2811aee 100644
--- a/README
+++ b/README
@@ -14,16 +14,17 @@
Executive Summary
~~~~~~~~~~~~~~~~~
-Valgrind is an award-winning instrumentation framework for building
-dynamic analysis tools. There are Valgrind tools that can automatically
-detect many memory management and threading bugs, and profile your
-programs in detail. You can also use Valgrind to build new tools.
+Valgrind is a framework for building dynamic analysis tools. There are
+Valgrind tools that can automatically detect many memory management
+and threading bugs, and profile your programs in detail. You can also
+use Valgrind to build new tools.
The Valgrind distribution currently includes six production-quality
-tools: a memory error detector, two thread error detectors, a cache and
-branch-prediction profiler, a call-graph generating cache profiler, and
-a heap profiler. It also includes two experimental tools: a
-heap/stack/global array overrun detector, and a SimPoint basic block vector
+tools: a memory error detector, two thread error detectors, a cache
+and branch-prediction profiler, a call-graph generating cache abd
+branch-prediction profiler, and a heap profiler. It also includes
+three experimental tools: a heap/stack/global array overrun detector,
+a different kind of heap profiler, and a SimPoint basic block vector
generator.
Valgrind is closely tied to details of the CPU, operating system and to
@@ -35,6 +36,7 @@
- AMD64/Linux
- PPC32/Linux
- PPC64/Linux
+- ARM/Linux
- x86/MacOSX
- AMD64/MacOSX
@@ -45,6 +47,9 @@
Valgrind is licensed under the GNU General Public License, version 2.
Read the file COPYING in the source distribution for details.
+However: if you contribute code, you need to make it available as GPL
+version 2 or later, and not 2-only.
+
Documentation
~~~~~~~~~~~~~
diff --git a/README_DEVELOPERS b/README_DEVELOPERS
index e08d872..9d523db 100644
--- a/README_DEVELOPERS
+++ b/README_DEVELOPERS
@@ -101,6 +101,21 @@
Steps (1)--(3) can be put in a .gdbinit file, but any directory names must
be fully expanded (ie. not an environment variable).
+A different and possibly easier way is as follows:
+
+(1) Run Valgrind as normal, but add the flag --wait-for-gdb=yes. This
+ puts the tool executable into a wait loop soon after it gains
+ control. This delays startup for a few seconds.
+
+(2) In a different shell, do "gdb /proc/<pid>/exe <pid>", where
+ <pid> you read from the output printed by (1). This attaches
+ GDB to the tool executable, which should be in the abovementioned
+ wait loop.
+
+(3) Do "cont" to continue. After the loop finishes spinning, startup
+ will continue as normal. Note that comment (3) above re passing
+ signals applies here too.
+
Self-hosting
~~~~~~~~~~~~
diff --git a/configure.in b/configure.in
index 88a9e10..80316ae 100644
--- a/configure.in
+++ b/configure.in
@@ -1449,7 +1449,9 @@
AM_CONDITIONAL([BUILD_LZCNT_TESTS], [test x$ac_have_as_lzcnt = xyes])
-
+# XXX JRS 2010 Oct 13: what is this for? For sure, we don't need this
+# when building the tool executables. I think we should get rid of it.
+#
# Check for TLS support in the compiler and linker
if test "x${cross_compiling}" = "xno"; then
# Native compilation: check whether running a program using TLS succeeds.
diff --git a/coregrind/m_main.c b/coregrind/m_main.c
index bea5258..e5871c4 100644
--- a/coregrind/m_main.c
+++ b/coregrind/m_main.c
@@ -237,7 +237,7 @@
"\n"
" %s is %s\n"
" Valgrind is Copyright (C) 2000-2010, and GNU GPL'd, by Julian Seward et al.\n"
-" LibVEX is Copyright (C) 2004-2010, and GNU GPL'd, by OpenWorks LLP.\n"
+" LibVEX is Copyright (C) 2004-2010, and GNU GPL'd, by OpenWorks LLP et al.\n"
"\n"
" Bug reports, feedback, admiration, abuse, etc, to: %s.\n"
"\n";
diff --git a/docs/xml/manual-core-adv.xml b/docs/xml/manual-core-adv.xml
index 10929b7..9eea68c 100644
--- a/docs/xml/manual-core-adv.xml
+++ b/docs/xml/manual-core-adv.xml
@@ -55,10 +55,10 @@
program with any extra supporting libraries.</para>
<para>The code added to your binary has negligible performance impact:
-on x86, amd64, ppc32 and ppc64, the overhead is 6 simple integer instructions
-and is probably undetectable except in tight loops.
-However, if you really wish to compile out the client requests, you can
-compile with <option>-DNVALGRIND</option> (analogous to
+on x86, amd64, ppc32, ppc64 and ARM, the overhead is 6 simple integer
+instructions and is probably undetectable except in tight loops.
+However, if you really wish to compile out the client requests, you
+can compile with <option>-DNVALGRIND</option> (analogous to
<option>-DNDEBUG</option>'s effect on
<function>assert</function>).
</para>
@@ -106,7 +106,7 @@
<para>
Alternatively, for transparent self-modifying-code support,
use<option>--smc-check=all</option>, or run
- on ppc32/Linux or ppc64/Linux.
+ on ppc32/Linux, ppc64/Linux or ARM/Linux.
</para>
</listitem>
</varlistentry>
@@ -567,7 +567,7 @@
<function>malloc</function> etc safely from within wrappers.
</para>
-<para>The above comments are true for {x86,amd64,ppc32}-linux. On
+<para>The above comments are true for {x86,amd64,ppc32,arm}-linux. On
ppc64-linux function wrapping is more fragile due to the (arguably
poorly designed) ppc64-linux ABI. This mandates the use of a shadow
stack which tracks entries/exits of both wrapper and replacement
@@ -578,7 +578,7 @@
possible to a limited depth, beyond which Valgrind has to abort the
run. This depth is currently 16 calls.</para>
-<para>For all platforms ({x86,amd64,ppc32,ppc64}-linux) all the above
+<para>For all platforms ({x86,amd64,ppc32,ppc64,arm}-linux) all the above
comments apply on a per-thread basis. In other words, wrapping is
thread-safe: each thread must individually observe the above
restrictions, but there is no need for any kind of inter-thread
diff --git a/docs/xml/manual-core.xml b/docs/xml/manual-core.xml
index 3ca9821..59eb787 100644
--- a/docs/xml/manual-core.xml
+++ b/docs/xml/manual-core.xml
@@ -130,11 +130,11 @@
is better to compile your program at its normal optimisation level.</para>
<para>Valgrind understands both the older "stabs" debugging format, used
-by GCC versions prior to 3.1, and the newer DWARF2 and DWARF3 formats
+by GCC versions prior to 3.1, and the newer DWARF2/3/4 formats
used by GCC
3.1 and later. We continue to develop our debug-info readers,
although the majority of effort will naturally enough go into the newer
-DWARF2/3 reader.</para>
+DWARF readers.</para>
<para>When you're ready to roll, run Valgrind as described above.
Note that you should run the real
@@ -1235,7 +1235,7 @@
<para>Be careful when
using <option>--dsymutil=yes</option>, since it will
cause pre-existing <computeroutput>.dSYM</computeroutput>
- directories to be silently deleted and re-created. Also note the
+ directories to be silently deleted and re-created. Also note that
<computeroutput>dsymutil</computeroutput> is quite slow, sometimes
excessively so.</para>
</listitem>
@@ -1390,13 +1390,13 @@
will likely lead to incorrect behaviour and/or crashes.</para>
<para>Valgrind has three levels of self-modifying code detection:
- no detection, detect self-modifying code on the stack (which used by
+ no detection, detect self-modifying code on the stack (which is used by
GCC to implement nested functions), or detect self-modifying code
everywhere. Note that the default option will catch the vast majority
of cases. The main case it will not catch is programs such as JIT
compilers that dynamically generate code <emphasis>and</emphasis>
subsequently overwrite part or all of it. Running with
- <varname>all</varname> will slow Valgrind down greatly. Running with
+ <varname>all</varname> will slow Valgrind down noticeably. Running with
<varname>none</varname> will rarely speed things up, since very little
code gets put on the stack for most programs. The
<function>VALGRIND_DISCARD_TRANSLATIONS</function> client request is
@@ -1408,11 +1408,11 @@
-->
</para>
- <para>Some architectures (including ppc32 and ppc64) require
+ <para>Some architectures (including ppc32, ppc64 and ARM) require
programs which create code at runtime to flush the instruction
cache in between code generation and first use. Valgrind
- observes and honours such instructions. Hence, on ppc32/Linux
- and ppc64/Linux, Valgrind always provides complete, transparent
+ observes and honours such instructions. Hence, on ppc32/Linux,
+ ppc64/Linux and ARM/Linux, Valgrind always provides complete, transparent
support for self-modifying code. It is only on platforms such as
x86/Linux, AMD64/Linux and x86/Darwin that you need to use this
option.</para>
@@ -1711,8 +1711,7 @@
<computeroutput>futex</computeroutput> and so on.
<computeroutput>clone</computeroutput> is supported where either
everything is shared (a thread) or nothing is shared (fork-like); partial
-sharing will fail. Again, any use of atomic instruction sequences in shared
-memory between processes will not work reliably.
+sharing will fail.
</para>
@@ -1756,16 +1755,15 @@
<para>We use the standard Unix
<computeroutput>./configure</computeroutput>,
<computeroutput>make</computeroutput>, <computeroutput>make
-install</computeroutput> mechanism, and we have attempted to
-ensure that it works on machines with kernel 2.4 or 2.6 and glibc
-2.2.X to 2.10.X. Once you have completed
+install</computeroutput> mechanism. Once you have completed
<computeroutput>make install</computeroutput> you may then want
to run the regression tests
with <computeroutput>make regtest</computeroutput>.
</para>
-<para>There are five options (in addition to the usual
-<option>--prefix</option> which affect how Valgrind is built:
+<para>In addition to the usual
+<option>--prefix=/path/to/install/tree</option>, there are three
+ options which affect how Valgrind is built:
<itemizedlist>
<listitem>
@@ -1778,24 +1776,16 @@
</listitem>
<listitem>
- <para><option>--enable-tls</option></para>
- <para>TLS (Thread Local Storage) is a relatively new mechanism which
- requires compiler, linker and kernel support. Valgrind tries to
- automatically test if TLS is supported and if so enables this option.
- Sometimes it cannot test for TLS, so this option allows you to
- override the automatic test.</para>
- </listitem>
-
- <listitem>
<para><option>--enable-only64bit</option></para>
<para><option>--enable-only32bit</option></para>
- <para>On 64-bit
- platforms (amd64-linux, ppc64-linux), Valgrind is by default built
- in such a way that both 32-bit and 64-bit executables can be run.
- Sometimes this cleverness is a problem for a variety of reasons.
- These two options allow for single-target builds in this situation.
- If you issue both, the configure script will complain. Note they
- are ignored on 32-bit-only platforms (x86-linux, ppc32-linux).
+ <para>On 64-bit platforms (amd64-linux, ppc64-linux,
+ amd64-darwin), Valgrind is by default built in such a way that
+ both 32-bit and 64-bit executables can be run. Sometimes this
+ cleverness is a problem for a variety of reasons. These two
+ options allow for single-target builds in this situation. If you
+ issue both, the configure script will complain. Note they are
+ ignored on 32-bit-only platforms (x86-linux, ppc32-linux,
+ arm-linux, x86-darwin).
</para>
</listitem>
@@ -1859,29 +1849,45 @@
<itemizedlist>
<listitem>
- <para>On x86 and amd64, there is no support for 3DNow! instructions.
- If the translator encounters these, Valgrind will generate a SIGILL
- when the instruction is executed. Apart from that, on x86 and amd64,
- essentially all instructions are supported, up to and including SSSE3.
+ <para>On x86 and amd64, there is no support for 3DNow!
+ instructions. If the translator encounters these, Valgrind will
+ generate a SIGILL when the instruction is executed. Apart from
+ that, on x86 and amd64, essentially all instructions are supported,
+ up to and including SSE4.2 in 64-bit mode and SSSE3 in 32-bit mode.
+ Some exceptions: SSE4.2 AES instructions are not supported in
+ 64-bit mode, and 32-bit mode does in fact support the bare minimum
+ SSE4 instructions to needed to run programs on MacOSX 10.6 on
+ 32-bit targets.
</para>
</listitem>
<listitem>
- <para>On ppc32 and ppc64, almost all integer, floating point and Altivec
- instructions are supported. Specifically: integer and FP insns that are
- mandatory for PowerPC, the "General-purpose optional" group (fsqrt, fsqrts,
- stfiwx), the "Graphics optional" group (fre, fres, frsqrte, frsqrtes), and
- the Altivec (also known as VMX) SIMD instruction set, are supported.</para>
+ <para>On ppc32 and ppc64, almost all integer, floating point and
+ Altivec instructions are supported. Specifically: integer and FP
+ insns that are mandatory for PowerPC, the "General-purpose
+ optional" group (fsqrt, fsqrts, stfiwx), the "Graphics optional"
+ group (fre, fres, frsqrte, frsqrtes), and the Altivec (also known
+ as VMX) SIMD instruction set, are supported. Also, instructions
+ from the Power ISA 2.05 specification, as present in POWER6 CPUs,
+ are supported.</para>
+ </listitem>
+
+ <listitem>
+ <para>On ARM, essentially the entire ARMv7-A instruction set
+ is supported, in both ARM and Thumb mode. ThumbEE and Jazelle are
+ not supported. NEON and VFPv3 support is fairly complete. ARMv6
+ media instruction support is mostly done but not yet complete.
+ </para>
</listitem>
<listitem>
<para>If your program does its own memory management, rather than
using malloc/new/free/delete, it should still work, but Memcheck's
- error checking won't be so effective. If you describe your program's
- memory management scheme using "client requests"
- (see <xref linkend="manual-core-adv.clientreq"/>), Memcheck can do
- better. Nevertheless, using malloc/new and free/delete is still the
- best approach.</para>
+ error checking won't be so effective. If you describe your
+ program's memory management scheme using "client requests" (see
+ <xref linkend="manual-core-adv.clientreq"/>), Memcheck can do
+ better. Nevertheless, using malloc/new and free/delete is still
+ the best approach.</para>
</listitem>
<listitem>
@@ -1902,25 +1908,32 @@
</listitem>
<listitem>
- <para>Memory consumption of your program is majorly increased whilst
- running under Valgrind. This is due to the large amount of
- administrative information maintained behind the scenes. Another
- cause is that Valgrind dynamically translates the original
- executable. Translated, instrumented code is 12-18 times larger than
- the original so you can easily end up with 50+ MB of translations
- when running (eg) a web browser.</para>
+ <para>Memory consumption of your program is majorly increased
+ whilst running under Valgrind's Memcheck tool. This is due to the
+ large amount of administrative information maintained behind the
+ scenes. Another cause is that Valgrind dynamically translates the
+ original executable. Translated, instrumented code is 12-18 times
+ larger than the original so you can easily end up with 100+ MB of
+ translations when running (eg) a web browser.</para>
</listitem>
<listitem>
<para>Valgrind can handle dynamically-generated code just fine. If
- you regenerate code over the top of old code (ie. at the same memory
- addresses), if the code is on the stack Valgrind will realise the
- code has changed, and work correctly. This is necessary to handle
- the trampolines GCC uses to implemented nested functions. If you
- regenerate code somewhere other than the stack, you will need to use
- the <option>--smc-check=all</option> option, and Valgrind will run more
- slowly than normal. Or you can add client requests that tell Valgrind
- when your program has overwritten code.</para>
+ you regenerate code over the top of old code (ie. at the same
+ memory addresses), if the code is on the stack Valgrind will
+ realise the code has changed, and work correctly. This is
+ necessary to handle the trampolines GCC uses to implemented nested
+ functions. If you regenerate code somewhere other than the stack,
+ and you are running on an 32- or 64-bit x86 CPU, you will need to
+ use the <option>--smc-check=all</option> option, and Valgrind will
+ run more slowly than normal. Or you can add client requests that
+ tell Valgrind when your program has overwritten code.
+ </para>
+ <para> On other platforms (ARM, PowerPC) Valgrind observes and
+ honours the cache invalidation hints that programs are obliged to
+ emit to notify new code, and so self-modifying-code support should
+ work automatically, without the need
+ for <option>--smc-check=all</option>.</para>
</listitem>
<listitem>
@@ -1997,6 +2010,19 @@
</listitem>
<listitem>
+ <para>Valgrind has the following limitations in
+ its implementation of ARM VFPv3 arithmetic, relative to
+ IEEE754.</para>
+
+ <para>Essentially the same: no exceptions, and limited observance
+ of rounding mode. Also, switching the VFP unit into vector mode
+ will cause Valgrind to abort the program -- it has no way to
+ emulate vector uses of VFP at a reasonable performance level. This
+ is no big deal given that non-scalar uses of VFP instructions are
+ in any case deprecated.</para>
+ </listitem>
+
+ <listitem>
<para>Valgrind has the following limitations
in its implementation of PPC32 and PPC64 floating point
arithmetic, relative to IEEE754.</para>
diff --git a/docs/xml/manual-intro.xml b/docs/xml/manual-intro.xml
index 452effd..3efbdee 100644
--- a/docs/xml/manual-intro.xml
+++ b/docs/xml/manual-intro.xml
@@ -54,6 +54,12 @@
</listitem>
<listitem>
+ <para><command>DHAT</command> is a different kind of heap
+ profiler. It helps you understand issues of block lifetimes,
+ block utilisation, and layout inefficiencies.</para>
+ </listitem>
+
+ <listitem>
<para><command>Ptrcheck</command> is an experimental heap, stack and
global array overrun detector. Its functionality overlaps somewhat
with Memcheck's, but it can find some problems that Memcheck would
diff --git a/docs/xml/quick-start-guide.xml b/docs/xml/quick-start-guide.xml
index 306c908..f7bbf68 100644
--- a/docs/xml/quick-start-guide.xml
+++ b/docs/xml/quick-start-guide.xml
@@ -48,7 +48,8 @@
idea, if you can tolerate the slowdown. With
<option>-O1</option> line numbers in error messages can
be inaccurate, although generally speaking running Memcheck on code compiled
-at <option>-O1</option> works fairly well.
+at <option>-O1</option> works fairly well, and the speed improvement
+compared to running <option>-O0</option> is quite significant.
Use of
<option>-O2</option> and above is not recommended as
Memcheck occasionally reports uninitialised-value errors which don't
diff --git a/docs/xml/vg-entities.xml b/docs/xml/vg-entities.xml
index bc6ea16..19a68e9 100644
--- a/docs/xml/vg-entities.xml
+++ b/docs/xml/vg-entities.xml
@@ -2,12 +2,12 @@
<!ENTITY vg-jemail "julian@valgrind.org">
<!ENTITY vg-vemail "valgrind@valgrind.org">
<!ENTITY cl-email "Josef.Weidendorfer@gmx.de">
-<!ENTITY vg-lifespan "2000-2009">
+<!ENTITY vg-lifespan "2000-2010">
<!-- valgrind release + version stuff -->
<!ENTITY rel-type "Release">
-<!ENTITY rel-version "3.5.0">
-<!ENTITY rel-date "19 August 2009">
+<!ENTITY rel-version "3.6.0">
+<!ENTITY rel-date "18 October 2010">
<!-- where the docs are installed -->
<!ENTITY vg-docs-path "$INSTALL/share/doc/valgrind/html/index.html">
diff --git a/massif/docs/ms-manual.xml b/massif/docs/ms-manual.xml
index 9e318c5..51f872b 100644
--- a/massif/docs/ms-manual.xml
+++ b/massif/docs/ms-manual.xml
@@ -688,6 +688,17 @@
</listitem>
</varlistentry>
+ <varlistentry id="opt.pages-as-heap" xreflabel="--pages-as-heap">
+ <term>
+ <option><![CDATA[--pages-as-heap=<yes|no> [default: no] ]]></option>
+ </term>
+ <listitem>
+ <para>Tells Massif to profile memory at the page level rather
+ than at the malloc'd block level. See above for details.
+ </para>
+ </listitem>
+ </varlistentry>
+
<varlistentry id="opt.depth" xreflabel="--depth">
<term>
<option><![CDATA[--depth=<number> [default: 30] ]]></option>
diff --git a/memcheck/docs/mc-manual.xml b/memcheck/docs/mc-manual.xml
index 4c75629..c380fce 100644
--- a/memcheck/docs/mc-manual.xml
+++ b/memcheck/docs/mc-manual.xml
@@ -763,7 +763,7 @@
<varlistentry id="opt.freelist-vol" xreflabel="--freelist-vol">
<term>
- <option><![CDATA[--freelist-vol=<number> [default: 10000000] ]]></option>
+ <option><![CDATA[--freelist-vol=<number> [default: 20000000] ]]></option>
</term>
<listitem>
<para>When the client program releases memory using
@@ -779,7 +779,7 @@
have been freed.</para>
<para>This option specifies the maximum total size, in bytes, of the
- blocks in the queue. The default value is ten million bytes.
+ blocks in the queue. The default value is twenty million bytes.
Increasing this increases the total amount of memory used by
Memcheck but may detect invalid uses of freed
blocks which would otherwise go undetected.</para>
@@ -1153,8 +1153,8 @@
<para>Each byte in memory has 8 associated V (valid-value) bits,
saying whether or not the byte has a defined value, and a single A
(valid-address) bit, saying whether or not the program currently has
- the right to read/write that address. (But, as mentioned above, heavy
- use of compression means the overhead is typically less than 25%.)</para>
+ the right to read/write that address. As mentioned above, heavy
+ use of compression means the overhead is typically around 25%.</para>
</listitem>
<listitem>
diff --git a/none/tests/cmdline1.stdout.exp b/none/tests/cmdline1.stdout.exp
index 7306e75..9c6d5fe 100644
--- a/none/tests/cmdline1.stdout.exp
+++ b/none/tests/cmdline1.stdout.exp
@@ -74,7 +74,7 @@
Nulgrind is Copyright (C) 2002-2010, and GNU GPL'd, by Nicholas Nethercote.
Valgrind is Copyright (C) 2000-2010, and GNU GPL'd, by Julian Seward et al.
- LibVEX is Copyright (C) 2004-2010, and GNU GPL'd, by OpenWorks LLP.
+ LibVEX is Copyright (C) 2004-2010, and GNU GPL'd, by OpenWorks LLP et al.
Bug reports, feedback, admiration, abuse, etc, to: www.valgrind.org.
diff --git a/none/tests/cmdline2.stdout.exp b/none/tests/cmdline2.stdout.exp
index 0d39df8..d27316f 100644
--- a/none/tests/cmdline2.stdout.exp
+++ b/none/tests/cmdline2.stdout.exp
@@ -125,7 +125,7 @@
Nulgrind is Copyright (C) 2002-2010, and GNU GPL'd, by Nicholas Nethercote.
Valgrind is Copyright (C) 2000-2010, and GNU GPL'd, by Julian Seward et al.
- LibVEX is Copyright (C) 2004-2010, and GNU GPL'd, by OpenWorks LLP.
+ LibVEX is Copyright (C) 2004-2010, and GNU GPL'd, by OpenWorks LLP et al.
Bug reports, feedback, admiration, abuse, etc, to: www.valgrind.org.