one (or a value near it) as "+1.0000e+00" instead of "+1.0000e-00".
Or it could be a rounding issue .. I dunno.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@8745
This gets rid of the messages "Approx: do_origins_Dirty(R): missed %d
bytes\n" and "Approx: do_origins_Dirty(W): missed %d bytes\n".
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@8719
memcheck/tests/Makefile.am and was copied into drd/tests/Makefile.am.
When building regtests for a 32-bit only build on a 64-bit CPU, the
use of $(VG_ARCH) in these Makefiles is incorrect, because VG_ARCH
will be set to the 64-bit architecture, not the 32-bit architecture.
See comments on VG_ARCH_PRI and VG_ARCH_MAX in configure.in for more
details.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@8623
relatively minor extensions to m_debuginfo, a major overhaul of
m_debuginfo/readdwarf3.c to get its space usage under control, and
changes throughout the system to enable heap-use profiling.
The majority of the merged changes were committed into
branches/PTRCHECK as the following revs: 8591 8595 8598 8599 8601 and
8161.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@8621
and moves the block even when the new size is smaller or the same.
This increases the chance that it can detect buggy code which assumes
that realloc-smaller doesn't cause the block to move.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@8454
temporary defined for every (original) temp used in the block's IR
preamble, as is already done of the shadow-definedness (V)
temporaries. Otherwise we can end up generating references to B
temporaries that have no assigned value, which causes the IR sanity
checker to complain. Only observed (and even then rarely) on the
complex preambles sometimes used for TOC-afflicted platforms.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@8450
memory report the actual addresses involved not just the size.
Based on patch from John Reiser <jreiser@BitWagon.com>.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@8440
blocks in the lc_shadows array. Such a situation could arise from
incorrect use of VALGRIND_MALLOCLIKE_BLOCK, and has been observed to
cause assertion failures for some runs of Wine on Valgrind.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@8144
Also, rename "ocache" to "ocacheL1" to be more consistent with the
comments and the rest of the otag cache code.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@8007
runs with --track-origins=yes), rather than having it statically
allocated. This is important because the cache is large (100MB) and
soaking up 100MB of address space for a non-tracking run is not good.
Unfortunately this slows down the origin tracker by 1 to 2 %.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7989
the primary map on 64-bit systems. Add extensive comments and
startup-time assertions.
As a result of this, fix two off-by-one errors in
MC_(helperc_MAKE_STACK_UNINIT) (unlikely to be of much significance,
but still ..). No other errors were found.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7988
* remove 'extern' in all the headers, as that is irrelevant and wastes
horizontal space
* fix some 64-bit uncleanness in client(-defined) block handling
* remove unneeded #includes
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7987
mc_errors.c, as it is relatively self contained. This reduces the
size of mc_main.c by about 1350 lines.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7986
support to Memcheck for tracking the origin of uninitialised values,
if you use the --track-origins=yes flag.
This currently causes some Memcheck regression tests to fail, because
they now print an extra line of advisory text in their output. This
will be fixed.
The core-tool interface is slightly changed. The version number for
the interface needs to be incremented.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7982
