|Producing memory traces of C storage allocation? email@example.com (2001-06-28)|
|Re: Producing memory traces of C storage allocation? firstname.lastname@example.org (Joachim Durchholz) (2001-07-02)|
|Re: Producing memory traces of C storage allocation? email@example.com (Graeme Roy) (2001-07-02)|
|Re: Producing memory traces of C storage allocation? firstname.lastname@example.org (2001-07-02)|
|Re: Producing memory traces of C storage allocation? email@example.com (Friedrich Dominicus) (2001-07-17)|
|From:||Friedrich Dominicus <firstname.lastname@example.org>|
|Date:||17 Jul 2001 23:27:09 -0400|
|Organization:||Q Software Solutions GmbH|
|Posted-Date:||17 Jul 2001 23:27:09 EDT|
email@example.com (Corndog) writes:
> Hmm..this is quite the question Im sure, but does anyone know of a C
> compiler or is anyone able to tell me how to create one (roars of
> laughter) that is able to force the program being generated to log all
> calls to memory allocation routines like malloc and free in order for
> me to be able to determine the size of the heap at any point during
> the program execution?
There are a bunch of libraries available which were designed for that
especially. I suggest you use your trusted search engine and check out
the different options.
> I figure the only way I can get the actual
> size of the heap at any given point in time is to have the compiler
> intercept the memory allocation routines and do the work of wrappers
> for me. Please help..puhlease!
Why do you need to know that BTW?
Return to the
Search the comp.compilers archives again.