|
From: David S. <da...@si...> - 2010-02-11 15:57:36
Attachments:
Makefile.am
|
hello all! i'm building a new tool, that tracks heap allocation/freeing. it will eventually give a visual representation (3d view) of the memory and allow a programmer to see where in the source code the memory came from (possibly tracking read/writes to it aswell). i'm trying to create a vgpreload_*.so for this tool. sofar i've simply adjusted visualdbg/Makefile.am, based on massif/Makefile.am. when i compile, vgpreload_*.so doesn't get created. is there anything else required to build vgpreload, or did i make some simple mistake (typo)? i've attached the Makefile for my tool. david |
|
From: Julian S. <js...@ac...> - 2010-02-11 16:31:06
|
On Thursday 11 February 2010, David Steiner wrote: > hello all! > > i'm building a new tool, that tracks heap allocation/freeing. it will > eventually give a visual representation (3d view) of the memory and allow a > programmer to see where in the source code the memory came from (possibly > tracking read/writes to it aswell). sounds cool. > i'm trying to create a vgpreload_*.so for this tool. sofar i've simply > adjusted visualdbg/Makefile.am, based on massif/Makefile.am. when i > compile, vgpreload_*.so doesn't get created. is there anything else > required to build vgpreload, or did i make some simple mistake (typo)? i've > attached the Makefile for my tool. It looks like it's a derivative of the Makefile for 'none', not Massif. 'none' doesn't use a preload file, so uh, maybe if you start over using massif/Makefile.am ? Or at least, consistently rename in your Makefile? atm there are three mentions of "NONE_SOURCES_COMMON", which can't be right. J |