On 11.03.22 11:34, Matthias Urlichs wrote:
On 11.03.22 11:14, Daniel-Constantin Mierla wrote:
Double frees are safe for kamailio
until they are not,
By cutting only the part you want and comment only around it, then you
start to misinform. If you want to add value for a conversation, keep
the whole context.
Double free is a safe operation in Kamailio, what leads to it can be an
issue, like I said in my "full" email previously.
Cheers,
Daniel
i.e. when (not if) something else manages to allocate
the memory in
question before the second "free" comes along, you have a problem.
How to proceed: replace the
shm_free(ptr);
at line 323 of tls_init.c with its macro expansion, i.e.
_shm_root.xfree(_shm_root.mem_block, (p), "shm", fname, fline,
"tls")
(or something along these lines) so that you get some idea of where
these "shm_free" calls originate.
This probably should also be done for the calls to malloc and realloc.
There's no good reason to throw away the debug information.
--
-- regards
--
-- Matthias Urlichs
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
*
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla --
www.asipto.com
www.twitter.com/miconda --
www.linkedin.com/in/miconda
Kamailio Advanced Training - Online
March 28-31, 2022 (Europe Timezone)
*
https://www.asipto.com/sw/kamailio-advanced-training-online/