History log of /external/valgrind/memcheck/tests/wrap1.c
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
5a6d7e4866b378affae75405e5d4c9e573677ac7 20-Jan-2006 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Wibble


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5574 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/wrap1.c
d68ac3e974d25f88492774f6baa491999afde9f9 20-Jan-2006 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Changes to make function wrapping work better on ppc64-linux:

- when recording the non-redirected address in guest_NRADDR, also
snapshot the current R2 value, as that will be needed to run the
original safely

- As a consequence, the original-function information extracted by
VALGRIND_GET_ORIG_FN is different on ppc64-linux (2 words) from
all other platforms (1 word). So change the type of it from
void* to a new type OrigFn which can be defined differently for
each platform.

- Change the CALL_FN_* macros for ppc64-linux to save/restore
R2 values appropriately.

- ppc64-linux: detect overflow/underflow of the redirect stack
and bring Valgrind to a halt if this happens

- Update VG_CLREQ_SZB for ppc32/64 (was out of date).





git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5569 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/wrap1.c
0ec07f32bbbb209d749b9974408e6f025ad40b31 12-Jan-2006 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Merge in function wrapping support from the FNWRAP branch. That
branch hereby becomes inactive. This currently breaks everything
except x86; fixes for amd64/ppc32 to follow.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5520 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/wrap1.c