asterisk users - Jan 2006 - RE: [Asterisk-Announce] Asterisk 1.2.4 and Zaptel 1.2.3

Does anyone know what date this memory leak was introduced and/or how to
check source code for it?

I am running a pre-1.2 CVS head version and would like to know if the
potential problem exists.
> -----Original Message-----
> From: asterisk-announce-bounces@lists.digium.com [mailto:asterisk-
> announce-bounces@lists.digium.com] On Behalf Of The Asterisk
Development
> Team
> Sent: Monday, January 30, 2006 9:34 PM
> To: asterisk-announce@lists.digium.com;
asterisk-users@lists.digium.com;
> Asterisk Developers Mailing List
> Subject: [Asterisk-Announce] Asterisk 1.2.4 and Zaptel 1.2.3
> 
> Asterisk 1.2.4 and Zaptel 1.2.3 have been released!
> 
> This update of Asterisk includes a fix for a significant memory leak
in
> the expression parser that is present in all previous releases of
> Asterisk 1.2. This version of Zaptel includes support for the new
> generation of VPM100M echo cancellation modules from Digium. For
further
> information about all changes that have been made, consult the
> appropriate ChangeLog in the tarball or on the ftp site.
> 
> Thank you!
> 
> -- The Asterisk Development Team
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
> 
> Asterisk-Announce mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-announce

Totally uneducated guess:  If your version has the expression parser, it has
the leak.

On 1/30/06, Damon Estep <damon@suburbanbroadband.net>
wrote:
>
> Does anyone know what date this memory leak was introduced and/or how to
> check source code for it?
>
> I am running a pre-1.2 CVS head version and would like to know if the
> potential problem exists.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20060131/d273161a/attachment.htm

Damon Estep wrote:
> Does anyone know what date this memory leak was introduced and/or how to
> check source code for it?
> 
> I am running a pre-1.2 CVS head version and would like to know if the
> potential problem exists.
It has been present since we switched to the 'new' expression parser a 
few months ago. If your system is using ast_expr2.c instead of 
ast_expr.c, you have the problem.