tree d8b6d5cd987e1383bdf938443839943689566bc7
parent 79d001fcb699ef13f15593f155af8f3051f56353
author Pau Espin Pedrol <pespin@sysmocom.de> 1614106313 +0100
committer Pau Espin Pedrol <pespin@sysmocom.de> 1614106503 +0100

Workaround ASan report memleak during call to --vty-ref-xml

For some unknown reason, using size=0 instead of 1 makes LeakSanitizer
report a leak when calling osmo-hnbgw --vty-ref-xml:
"""
==19857==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 96 byte(s) in 1 object(s) allocated from:
    #0 0x7f083b4d0d28 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.3+0xc1d28)
    #1 0x7f083a8e5661 in talloc_named_const (/usr/lib/x86_64-linux-gnu/libtalloc.so.2+0x6661)
"""

It seems iu_client.c is already using size=1.

Change-Id: I383653c981e68a053babd33dee1f0df8731752b0