|
From: John V. <jp...@ho...> - 2004-07-13 18:34:17
|
Hi, I'm new to valgrind (3 days use) but I've already found it to be very useful, so a big thanks. The "-fcheck-memory-usage" option that used to exist in gcc was also very useful to me, since I could write my own checking routines with application-specific knowledge about when memory should and should not be accessed. Since this is no longer available in gcc, I wonder if it might be possible to implement similar "hooks" via the valgrind core? Thanks again for a great tool! /John. _________________________________________________________________ It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger |
|
From: Nicholas N. <nj...@ca...> - 2004-07-17 08:47:29
|
On Tue, 13 Jul 2004, John Vincent wrote: > I'm new to valgrind (3 days use) but I've already found it to be very useful, > so a big thanks. Glad you like it! > The "-fcheck-memory-usage" option that used to exist in gcc was also very > useful to me, since I could write my own checking routines with > application-specific knowledge about when memory should and should not be > accessed. Since this is no longer available in gcc, I wonder if it might be > possible to implement similar "hooks" via the valgrind core? Have you read sections 2.7 and 3.7 of the manual, about client requests? If I understand correctly, this is exactly what you want. N |