On Mon, Mar 9, 2009 at 6:43 AM, Gordan Bobic
<address@hidden> wrote:
On Mon, 9 Mar 2009 10:08:58 +0530, Vikas Gorur <address@hidden> wrote:
> 2009/3/8 Gordan Bobic <address@hidden>:
>> I've been looking through the source code, trying to track down that big
>> memory leak. Can somebody tell me where the node calloc() on line 1713
in
>> y.tab.c (2.0.0rc2) gets free()-ed? I can see that node gets assigned to
>> tree, and then in section_end, there is tree = NULL. Am I missing the
>> cleanup happening somewhere else?
>
> It isn't free'd, but it cannot be the source of the 'big' memory leak.
> y.tab.c is for the parsing of the spec file, which happens only once,
> and the calloc's are fairly small.
Fair enough. Consider it a bug report, then, even if it's not the bug I was
looking for. ;)