[SR-Users] how to turn off memory debug messages?

[Daniel-Constantin Mierla]

On 26.04.21 17:09, Juha Heinanen wrote:
> Now I have MEMDBG=1 and lots of these kind of messages show up when
> Kamailio fails to start due to sqlpos failing to connect to server:
>
> Apr 26 18:06:30 edge /usr/bin/edge-proxy[8548]: CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f7c80b347b0), called from tls: tls_init.c: ser_free(323), first free tls: tls_init.c: ser_malloc(293) - ignoring
> Apr 26 18:06:30 edge /usr/bin/edge-proxy[8548]: CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f7c80b306b0), called from tls: tls_init.c: ser_free(323), first free tls: tls_init.c: ser_malloc(293) - ignoring
> Apr 26 18:06:30 edge /usr/bin/edge-proxy[8548]: CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f7c80b34a30), called from tls: tls_init.c: ser_free(323), first free tls: tls_init.c: ser_free(323) - ignoring
> Apr 26 18:06:30 edge /usr/bin/edge-proxy[8548]: CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f7c80b39b90), called from tls: tls_init.c: ser_free(323), first free tls: tls_init.c: ser_malloc(293) - ignoring

They are from libssl, because kamailio sets it own memory manager for
libssl, likely to be from the libmysqlclient connection, if you connect
to the database sever via tls.

Unless one wants to dig in further in libssl or libmysqlclient (or
mariadb), they have to be ignored being the case of failed
startup/misconfiguration which is not the usual case, or make an option
to print them at the different log level.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - Online
May 17-20, 2021 (Europe Timezone) - June 7-10, 2021 (America Timezone)
  * https://www.asipto.com/sw/kamailio-advanced-training-online/