History log of /external/valgrind/memcheck/tests/leak-segv-jmp.c
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
e27c8cd24643d09ef7857a567771a95e888b6b5f 15-Apr-2015 zliu <zliu@a5019735-40e9-0310-863c-91ae7b9d1cf9> To address memcheck/tests/leak-segv-jmp test failure for TILEGX
By: Zhi-Gang Liu zhg.liu@gmail.com


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15097 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/leak-segv-jmp.c
112711afefcfcd43680c7c4aa8d38ef180e8811e 10-Apr-2015 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Add a port to Linux/TileGx. Zhi-Gang Liu (zliu@tilera.com)
Valgrind aspects, to match vex r3124.

See bug 339778 - Linux/TileGx platform support to Valgrind



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15080 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/leak-segv-jmp.c
7a76f4b27db3ec7a0130a5fd7120aeb5060c89c2 06-Oct-2013 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fix leak scan SEGV catcher when ptr starts in unreadable page (readable for aspacemgr)

The fault catcher installed during leak scan to catter e.g. for
possible desynchronisation between real protection and aspacemgr
was not activated when the scanned ptr was directly pointing in
a desynchronised page.
This was (initially only) visible on ppc32 (gcc110) as the page size of
gcc110 is big (64 K).

=> modified the leak-segv-jmp test so as to produce the problem also
on systems with smaller pages.

The fix consists in calling the setjmp before the scan loop,
and skip the bad address which has been recorded by the fault
catcher.
Also, deemed better to just skip one single Addr rather than a full page
(e.g. to skip less data in case some addresses are unreadable e.g.
on strange hardware).

Performance of the leak scan has been measured, seems slightly
faster on x86,amd64 and ppc32. Slightly slower on ppc64.

Also if verbose argument is given, outputs the nr of bytes skipped
due to fault.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13623 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/leak-segv-jmp.c
e37c4bce28e78b9288458907357989bfacd265e7 04-Oct-2013 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fix compilation problem of memcheck/tests/leak-segv-jmp on ppc32
With the change, the test compiles on ppc32.
However, the test fails miserably with
Segmentation fault
while the whole purpose of the test was to see the leak search
would *not* segfault.

More investigations needed, but still committing as is to let
the tests compile and run.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13612 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/leak-segv-jmp.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/leak-segv-jmp.c
ec587b07a0d13a6dc6fab184dfb98f0dec841f18 17-Jul-2013 dejanj <dejanj@a5019735-40e9-0310-863c-91ae7b9d1cf9> mips64: Add a test case for mips64.

Add a function in the memcheck/tests/leak-segv-jmp.c for MIPS64
that execute the syscall. Because we added the mips64 case we
need to change the line number in *.exp file.
Fixes memcheck/tests/leak-segv-jmp for MIPS64.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13456 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/leak-segv-jmp.c
2082b3436bd570f764945258654bd2152ec1a7de 24-Sep-2012 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Unbreak build on Mac_OS where __NR_mprotect is not defined.
The test is not executed on Darwin but should compile.
(based on fix suggestion by Rich Coe)



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13014 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/leak-segv-jmp.c
21fcbb73c60e6eabbccf877439c095cf3b7c66cf 14-Sep-2012 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Add a test which checks the leak search recovery mechanism

The leak search must recover if unreadable pages are scanned.
This test creates such unreadable pages by doing non SIMD mprotect
syscall (not seen by the aspacemgr).



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12972 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/leak-segv-jmp.c