On Wed, 2014-03-19 at 13:50 +0000, Tom Hughes wrote: > On 19/03/14 12:45, Ashoka K wrote: > on the device. Device is ARM OMAP running Linux-2.6.33 cross compiled. > > > > I tested and found that summary of valgrind output is shown only on > > graceful exit of > > the application. Tested with a small memleak program as described in > > Valgrind > > documentation. > > Memory leaks are only reported when the program finishes, unless you use > a client request to ask for a check.
You can also trigger leak check from shell script (or from gdb), using vgdb. e.g. vgdb leak_check full possible increased will do a leak check, showing the possibly and definitely leaked loss records that have increased since the previous leak check. Philippe ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
