History log of /external/valgrind/memcheck/tests/origin5-bz2.c
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
46cc04521acf2827eb33310fadc119bf2dc039e4 25-Oct-2014 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Merge r14202 from the BUF_REMOVAL branch to trunk.
This patch changes the interface and behaviour of VG_(demangle) and
VG_(maybe_Z_demangle). Instead of copying the demangled name into a
fixed sized buffer that is passed in from the caller (HChar *buf, Int n_buf),
the demangling functions will now return a pointer to the full-length
demangled name (HChar **result). It is the caller's responsiblilty to
make a copy if needed.

This change in function parameters ripples upward
- first: to get_sym_name
- then to the convenience wrappers
- VG_(get_fnname)
- VG_(get_fnname_w_offset)
- VG_(get_fnname_if_entry)
- VG_(get_fnname_raw)
- VG_(get_fnname_no_cxx_demangle)
- VG_(get_datasym_and_offset)

The changes in foComplete then forces the arguments of
- VG_(get_objname) to be changed as well

There are some issues regarding the ownership and persistence of
character strings to consider.
In general, the returned character string is owned by "somebody else"
which means the caller must not free it. Also, the caller must not
modify the returned string as it possibly points to read only memory.
Additionally, the returned string is not necessarily persistent. Here are
the scenarios:
- the returned string is a demangled function name in which case the
memory holding the string will be freed when the demangler is called again.
- the returned string hangs off of a DebugInfo structure in which case
it will be freed when the DebugInfo is discarded
- the returned string hangs off of a segment in the address space manager
in which case it may be overwritten when the segment is merged with
another segment
So the rule of thunb here is: if in doubt strdup the string.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14664 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/origin5-bz2.c
06bc722457ffe12e056d2f40d0d2f5c8711b541f 02-Oct-2013 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Silence clang warnings about uninitialised and unused values in
memcheck testcases.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13599 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/origin5-bz2.c
7fc4d4aedc82a0403d26736f7c61b02e50c85a16 26-Oct-2011 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Give function copy_input_until_stop the noinline atribute.
At least one of the compilers for s390x nightly builds was inlining it.
Update exp files accoordingly. This should fix any residual back-trace
noise for this testcase.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12235 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/origin5-bz2.c
d3e4dd9f322e1746ee90fb9363d11654c5101502 23-Jan-2009 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Merge some minor regtest updates from the DARWIN branch:
- avoid using <malloc.h> where it's not necessary, because on DARWIN it's
called <malloc/malloc.h>
- filter the output of brk2 more, which allows the .stderr.exp2 file to be
removed.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@9037 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/origin5-bz2.c
f5049f7037c3d9e4b376d87c62a943da4de5509b 08-Nov-2008 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Attempt to reduce output variance by ensuring mainSort() is never inlined.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@8744 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/origin5-bz2.c
7cf4e6b6aed533af53339f36099ed244dc4a5b7f 01-May-2008 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Merge branches/OTRACK_BY_INSTRUMENTATION into the trunk. This adds
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 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/origin5-bz2.c