|
From: Rich C. <rc...@wi...> - 2013-01-17 13:44:43
|
I would take the file Heap.cpp and construct a small test case, main.cpp that initializes Heap exactly like your failing program. Cut out everything that is not relevant to the problem. Get this new code to fail with valgrind. Then send the source code to the list and the steps to reproduce the problem so we can see what you see. Rich On Fri, 11 Jan 2013 12:56:53 +0530 Muthumeenal Natarajan <mna...@ai...> wrote: > Hi, > > Pls find attached the Mem stats output from valgrind, attached both the versions (one without the patch and one with the patch which helps to increase the memory from http://sourceforge.net/mailarchive/message.php?msg_id=30299697) > > Memory stats look the same in both the cases and it's not about increasing the memory as we allocate very low (22MB) which terminates the process while running with valgrind. > > Can you pls redirect us if you have already faced similar issues or is there any settings which can bypass this cause we may not be able to reduce this size, as we need them for our project. > > Thanks, > Meenal > > From: Kalaivani R [mailto:kal...@gm...] > Sent: Friday, January 11, 2013 11:05 AM > To: Muthumeenal Natarajan > Subject: Fwd: [Valgrind-developers] Need help : to prevent valgrind from terminating due to SIGSEGV > > > ---------- Forwarded message ---------- > From: Philippe Waroquiers <phi...@sk...<mailto:phi...@sk...>> > Date: Fri, Jan 11, 2013 at 1:02 AM > Subject: Re: [Valgrind-developers] Need help : to prevent valgrind from terminating due to SIGSEGV > To: Kalaivani R <kal...@gm...<mailto:kal...@gm...>> > > On Fri, 2013-01-11 at 00:47 +0530, Kalaivani R wrote: > > > > > Today we tried to reduce the amount of memory allocated from HEAP for > > our binary by reducing the allocations and then the valgrind seems to > > work fine with the same executable.. > So, this seems to point at using a lot of memory. > > Which version of Valgrind are you using ? > Better use the last released version (3.8.1) as there was > some memory use improvements in recent versions. > > > > Is there a way to figure out how much memory valgrind is consuming > > while running with our exe? > To see what is going on, restart your program giving the flags > --stats=yes --profile-heap=yes to Valgrind. > With this, Valgrind will report various detailed statistics about > memory usage (for the client process, and for the Valgrind internals). > The memory of Valgrind is divided in "arenas". > Post the last statistics for each arena. > Typically, one arena stat looks like: > -------- Arena "core": 1048576/1048576 max/curr mmap'd, 0/0 unsplit/split sb unmmap'd, 112800/112800 max/curr on_loan 4 rzB -------- > 16 in 1: stacks.rs.1 > 40 in 1: gdbserved_watches > 72 in 1: main.mpclo.3 > 1,008 in 71: errormgr.sLTy.1 > 2,592 in 81: errormgr.losf.1 > 2,880 in 81: errormgr.losf.2 > 3,216 in 81: errormgr.losf.4 > 4,440 in 175: errormgr.sLTy.2 > 33,000 in 6: gdbsrv > 65,536 in 1: di.syswrap-x86.azxG.1 > > > > > Is this patch required if more heap memory is consumed? > It should (or could?) help. To be confirmed based on the above stats. > > Philippe > > > > > > -- > Cheers, > Kalai -- Rich Coe rc...@wi... |