History log of /external/valgrind/perf/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/perf/bz2.c
83b62cbbab29bde83eba40231f307c2a311e73c8 15-Apr-2009 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Merge r9533..9536 (add tests/{asm.h,sys_mman.h,malloc.h} from the DARWIN
branch.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@9537 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/perf/bz2.c
43c48b6fa0fa17acf31123b8a143e83cbff2c4a1 27-Aug-2007 dirk <dirk@a5019735-40e9-0310-863c-91ae7b9d1cf9> updating licensing wording


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@6782 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/perf/bz2.c
cd030b59fd308ea5450bb1209ba18efc4c84f295 17-Oct-2006 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Merge r6121: Don't define uchar; it might already be defined.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@6260 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/perf/bz2.c
46712cd593e0c9ddf48431635e5b3e84a4eb1f42 22-Jan-2006 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Use the bz2 test in perf/ as a regression-test, just as a moderately
complex integer program which exercises Vex a bit.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5585 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/perf/bz2.c
86c2349f3dd6574a20f58b31ed901d0006bced4b 13-Dec-2005 njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> Add two new programs to the performance suite.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5326 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/perf/bz2.c