|
From: WAROQUIERS P. <phi...@eu...> - 2011-12-09 09:49:01
|
> If you modify the source i think you can > Look at VALGRIND_DO_LEAK_CHECK in link below > > http://valgrind.org/docs/manual/mc-manual.html <http://valgrind.org/docs/manual/mc-manual.html> > to be able to call incremental leak check Incremental leak check (i.e. showing the new or changed leaks since the previous search) is availalbe (from Valgrind 3.7.0) using the client requests VALGRIND_DO_ADDED_LEAK_CHECK and VALGRIND_DO_CHANGED_LEAK_CHECK . You can also trigger a leak check from the shell command line using vgdb. E.g. to show all the details about the new leaks since the previous seach, you type in a shell: vgdb leak_check increased. You can also (again with Valgrind 3.7.0) interactively use gdb together with Valgrind to put breakpoints at relevant places in your program, and call the monitor command "leak_check" to trigger leak check where you want. Philippe ____ This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender. |