[SR-Users] [PATCH] Memory corruption using s.subst transformation

Daniel-Constantin Mierla miconda at gmail.com
Mon May 13 09:35:03 CEST 2013


Hello,

On 5/10/13 9:53 AM, Juha Heinanen wrote:
> Daniel wrote:
>
>    please do the patch to store the new value in _tr_buffer and attach it
>    to mailing list or bug tracker. I haven't looked at code yet, but sounds
>    like there is indeed an issue. I will review the patch and apply it.
>
> What was the conclusion about this?  Was the patch ever submitted and
> applied?  If not, is the bug still there or has is been fixed by some
> other means?  I'm asking because this looked like a quite serious
> issue.
it was a patch that solved only for one case ( $var(x) = 
$(var(x){trans}) ), my comment on it what that it seems incomplete. If 
no patch shows up soon, I will just do it myself, not being something 
that big.

Thinking more of it, there are some corner cases when the same variabale 
is set with some transformation of it (not all transformations). If the 
expression on the right of the assignment has more that the variable and 
transformation, the it is not affected. Also, not all variables are 
exposed even when only with right side is the variable and transformation.

For example:
$var(x) = $(var(x){s.substr...}); --- is affected
$var(x) = $(var(x){s.substr...}) + "abc"; --- is not affected

Cheers,
Daniel

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, San Francisco, USA - June 24-27, 2013
   * http://asipto.com/u/katu *




More information about the sr-users mailing list