f5194b352c74cba18ba0e628567fd8183f0a6048 |
|
05-Jul-2011 |
sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> |
GDB server: fix tests following recent commits. Fixes #276987. (Philippe Waroquiers, philippe.waroquiers@skynet.be) * make_local_links - disable gdb tests if gdb version < 7 - disable pic tests if gdb version < 7.1 * nlfork_chain test - reduce chain from 20 to 15 to avoid ENOMEM on small ARM systems * main_pic.c - put break at line 11 rather than main entry, as ARM gdb does not properly show main args till it has started executing. * passsigalrm.c - do not setsa.sa_restorer (obsolete on linux, unknown on darwin) * mcvabits.vgtest - make prereq consistent with other tests * filter_gdb - upgraded filter to new linenr in clean_after_fork.c git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11853 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/gdbserver_tests/fork_chain.c
|
1ac21102f27aee0114733566ef4abd559051c5da |
|
15-Jun-2011 |
sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> |
Fix safe_fd exhaustion in fork chain caused by non closing of shared_mem_fd Patch that fixes the problem reported by Christian Borntraeger. The problem was created by keeping the shared memory mapped file opened without reason till the process does an exec. In case of a chain of forked processes (without exec), the range of safe_fd reserved for Valgrind own usage becomes exhausted. * coregrind/m_gdbserver/remote-utils.c : do not VG_(safe_fd) shared_mem_fd (as it is now closed directly) close shared_mem_fd once file is mmap-ed and written. * gdbserver_tests/nlfork_chain.stderr.exp,nlfork_chain.vgtest, fork_chain.c,nlfork_chain.stdout.exp: new files * gdbserver_tests/Makefile.am: modified for new nlfork_chain test (patch from #214909 c 103, Philippe Waroquiers, philippe.waroquiers@skynet.be) git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11818 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/gdbserver_tests/fork_chain.c
|