On Mon, 2013-11-18 at 11:40 +0100, Benjamin Schindler wrote: > Hi > > I just upgraded to valgrind 3.9.0 (debian sid backport). Most features > work, but helgrind hangs with my application, and starts to fill up > memory until the system starts swapping badly. This did not happen with > 3.8. I tried with and without the suppressions file I'm using but that > doesn't help. > The only thing that might be an issue is that the application uses cuda > and helgrind used to throw a lot of errors concerning cuda (all of which > I dealt with using a suppression file) > > Is this something known or is there a way I can debug this further?
You can try several things to get more info about what is going on: * run with --profile-heap=yes This will regularly provide details about who allocates what * together with the above, you can also use gdb+vgdb to debug your app running under valgrind, and use monitor v.info memory aspacemgr to get memory details at selected places. It might be interesting to do the above with 3.8.1 and 3.9 and look at the differences. Note that in 3.9.0, several arenas (kind of memory zones of the valgrind allocator) have been merged together. Philippe ------------------------------------------------------------------------------ Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users