* Marc-André Lureau (marcandre.lur...@redhat.com) wrote:
> Fix leak spotted by ASAN:
>
> Direct leak of 16 byte(s) in 1 object(s) allocated from:
> #0 0x7fe1abb80a38 in __interceptor_calloc (/lib64/libasan.so.4+0xdea38)
> #1 0x7fe1aaf1bf75 in g_malloc0 ../glib/gmem.c:124
> #2 0x7fe1aaf
On Wed, Mar 21, 2018 at 12:36:44PM +0100, Marc-André Lureau wrote:
> Fix leak spotted by ASAN:
>
> Direct leak of 16 byte(s) in 1 object(s) allocated from:
> #0 0x7fe1abb80a38 in __interceptor_calloc (/lib64/libasan.so.4+0xdea38)
> #1 0x7fe1aaf1bf75 in g_malloc0 ../glib/gmem.c:124
> #2
On 03/21/2018 12:36 PM, Marc-André Lureau wrote:
> Fix leak spotted by ASAN:
>
> Direct leak of 16 byte(s) in 1 object(s) allocated from:
> #0 0x7fe1abb80a38 in __interceptor_calloc (/lib64/libasan.so.4+0xdea38)
> #1 0x7fe1aaf1bf75 in g_malloc0 ../glib/gmem.c:124
> #2 0x7fe1aaf1c249 in
Fix leak spotted by ASAN:
Direct leak of 16 byte(s) in 1 object(s) allocated from:
#0 0x7fe1abb80a38 in __interceptor_calloc (/lib64/libasan.so.4+0xdea38)
#1 0x7fe1aaf1bf75 in g_malloc0 ../glib/gmem.c:124
#2 0x7fe1aaf1c249 in g_malloc0_n ../glib/gmem.c:355
#3 0x55f4841cfaa9 in post