11 Mar
2022
11 Mar
'22
11:34 a.m.
On 11.03.22 11:14, Daniel-Constantin Mierla wrote:
Double frees are safe for kamailio
until they are not, 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