I am not sure I followed your instructions correctly, but I think that did it.
> cat foo #!/bin/sh ulimit -n 100000 > ulimit -n 1024 > valgrind --log-file=/tmp/log ./foo ./foo: line 2: ulimit: open files: cannot modify limit: Operation not permitted > ulimit -n 100010 > ulimit -n 100010 > valgrind --log-file=/tmp/log ./foo > echo $? 0 Thanks Dan. And thanks Tom. -----Original Message----- From: daniel.r.ke...@gmail.com [mailto:daniel.r.ke...@gmail.com] On Behalf Of Dan Kegel Sent: Monday, October 06, 2014 7:08 PM To: Skarakis, Konstantinos Cc: Tom Hughes; valgrind-users@lists.sourceforge.net Subject: Re: [Valgrind-users] ulimit under valgrind What if you use ulimit on the outside, before valgrind runs, and raise the soft limit to 10 higher than your inner script would? ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
