@miconda Makes sense. No need to malloc/free if it isn't absolutely required for a
commonly used code path. I'll look over the patch and see if I can see a better
approach(using flags to signify malloced pointer). One of the larger concerns here was
that clang's address sanitizer was pointing out that at least one of the cases there
was a pointer to stack memory being returned, which could lead to bad things as that stack
frame was used by another thread.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/611#issuecomment-218471897