"Marko Kreen" <[EMAIL PROTECTED]> writes:
> On 9/1/08, Marko Kreen <[EMAIL PROTECTED]> wrote:
>> First a correction, overriding malloc/free seems dangerous they
>> seems to leak out, so correct would be to use YYMALLOC/YYFREE.
>> This leaves 1.875 potentially leaking, but danger seems small.
> Here is the safer patch. As the chance for the leak is rare,
> leaving 1.875 vulnerable should not be problem.
Actually, 1.875 appears to default to using alloca() when available,
so the issue doesn't even arise if you're building with gcc. (This
is probably why I'd never noticed a problem in this area.)
I thought that we might have an issue with flex as well, but so far as
I can tell there's no real problem given our current usage style for
the lexers.
Applied to all the backend .l files ...
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
