Function counting script
segin2005 at gmail.com
Sun Mar 19 13:40:34 CST 2006
Jim White wrote:
> Joris Huizer wrote:
>> Segin wrote:
>>> It's not a C interpeter, it's literally a frint end of sorts to
>>> grep. There's only one textual occurence of malloc() in the code, so
>>> it only returns one.
>>> Think before you speak.
>>> P.S. I'll add a C interpeter when there becomes a need for one.
>> It was my impression that the goal was to find leaks by counting
>> allocating and freeing of memory;
>> My example was about that: the counts do not have to indicate correct
>> usage of malloc()/free()
>> Sorry if this was an incorrect assumption
> Right. And by reading the code that is doing alloc/free you can
> determine if they are balanaced. But first you have to *find* where
> those calls are made.
This gives me an idea: I can add a command line flag to determine how to
invoke grep (e.g. just a count, or a count plus occurences by line)
More information about the wine-devel