Re: [Valgrind-users] massif & counts per type

2020-09-12 Thread folkert
> Anyhow, it sounds like you are starting to reinvent heaptrack - it does > exactly the above and then some. Indeed it does: I looked at and it is perfectly for my use-case. Thank you! ___ Valgrind-users mailing list

Re: [Valgrind-users] valgrind always fails with out of memory

2020-09-12 Thread Philippe Waroquiers
On Tue, 2020-09-08 at 14:09 +0200, Mario Emmenlauer wrote: > On 08.09.20 12:25, Mario Emmenlauer wrote: > > On 08.09.20 12:04, Mario Emmenlauer wrote: > > > The error I get most frequently is (full output attached in log.txt) > > > ==32== Valgrind's memory management: out of memory: > > >

Re: [Valgrind-users] massif & counts per type

2020-09-12 Thread Philippe Waroquiers
On Fri, 2020-09-11 at 12:38 +0200, Milian Wolff wrote: > And finally, with heaptrack it is also not yet easily doable to get a diff > between two time stamps. Also a feature I've long thought about implementing, > but never got around to... Note that valgrind allows to report a "delta/diff"

Re: [Valgrind-users] massif & counts per type

2020-09-12 Thread Philippe Waroquiers
On Thu, 2020-09-10 at 15:26 +0200, folkert wrote: > Hi, > > How can I obtain the number of mallocs per type in a time-frame using > massif? I'm NOT interested in the total in use, I would like to know how > often type x is allocated between t+1 and t+2. You could run your application under