|
From: Konstantin S. <kon...@gm...> - 2011-01-12 09:05:42
|
The failure happens when chrome tries to fork/exec itself via /proc/self/exe link. This sounds unfriendly to valgrind, since /proc/self/exe points to memcheck instead of chrome. Right? Any suggestion how to workaround this (other than removing /proc/self/exe from the chrome source code)? Thanks! --kcc On Wed, Jan 12, 2011 at 8:23 AM, Konstantin Serebryany < kon...@gm...> wrote: > > > On Tue, Jan 11, 2011 at 6:50 PM, John Reiser <jr...@bi...> wrote: > >> > The error happens only when I run a tree of processes under 'valgrind >> > --trace-children=yes'. >> >> Is the system running out of memory resources? > > No. The set of processes doesn't take more than half of available RAM. > >> When the mmap() fails then >> > > mmap doesn't fail -- it does not get called. > am_mmap_named_file_fixed_client exits before calling mmap > > > --kcc > > >> copy the contents of /proc/meminfo onto stderr. (Make a subroutine >> and use it to print out both /proc/self/maps and /proc/meminfo.) >> >> -- >> >> >> ------------------------------------------------------------------------------ >> Gaining the trust of online customers is vital for the success of any >> company >> that requires sensitive data to be transmitted over the Web. Learn how >> to >> best implement a security strategy that keeps consumers' information >> secure >> and instills the confidence they need to proceed with transactions. >> http://p.sf.net/sfu/oracle-sfdevnl >> _______________________________________________ >> Valgrind-developers mailing list >> Val...@li... >> https://lists.sourceforge.net/lists/listinfo/valgrind-developers >> > > |