On 18/07/12 10:03, daniel.jan...@edgeware.tv wrote: > Thanks, running "ulimit -n 100000" seems to fix my problem. It's strange > though since the program under test sets its own limit RLIMIT_NOFILE with > setrlimit().
Does it check the return value? I suspect it doesn't ;-) To explain, because valgrind reserves some file descriptors for itself at the top end of the range it also refuses attempts to change the limit because to do so it would have to move it's own descriptors. So you should find that the setrlimit call returns EPERM if you try and change the hard limit when under valgrind. Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
