Hi Andreas,
you are right - the problem was not the string itself, but the str
itself. Anyhow, hopefully is fixed now.
regards,
bogdan
Andreas Granig wrote:
Bogdan,
However, another problem accured.
I see in my logs after an INVITE:
set_dst_uri: Not enough memory
lookup(): Failed to set dst_uri of Path
In my original patch I made a copy of "route->nameaddr.uri" in
get_path_dst_uri() of modules/registrar/path.c and then free'd the
parsed route, but your optimization just points to that uri and also
free's that route, which invalidates the pointer to that uri, as far
as I understand.
Can you please check that again, because if I comment out the
"free_rr(&route)", it does work (although it creates a mem-leak).
Andy