[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Memory leak in bison 1.35
From: |
Akim Demaille |
Subject: |
Re: Memory leak in bison 1.35 |
Date: |
27 Aug 2002 16:18:16 +0200 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Honest Recruiter) |
>>>>> "Tim" == Tim Van Holder <address@hidden> writes:
Tim> On Tue, 2002-08-27 at 12:34, Ignasi Villagrasa wrote:
>> Hi everyone,
>>
>> I'm using bison version 1.35 that comes with cygwin package for
>> Windows enviroments.
>>
>> I detect a memory leak in generated C code. Function yyparse loses
>> periodically 4K chunks memory.
>>
>> Because of the unclear generated code, I'd like to know if there's
>> a known solution for this problem before getting into the source
>> code.
Tim> Are you also using flex? At startup, flex allocates a buffer
Tim> that is never freed; it's not really a memory leak (flex merely
Tim> has no point at which it can free the buffer normally, so it
Tim> relies on the normal 'at end' cleanup), but will be reported as
Tim> such by many memory checkers. It allocates chunks of 16k tho,
Tim> not 4k.
Hm, are you sure it is really yyparse per se which is guilty, and not
the user actions themselves?