summaryrefslogtreecommitdiff
path: root/logview/logview-manager.c
diff options
context:
space:
mode:
authorrbuj <[email protected]>2019-03-04 07:29:38 +0100
committermonsta <[email protected]>2019-05-29 11:29:16 +0300
commit10d0e538235a3d87c8a5c64193cbcf04c2a8a07b (patch)
treed15ff2c659bc7321c734df7e30ed5a112fd9d061 /logview/logview-manager.c
parent817420c99454b35eebef385bdf2ba6b2a1dbafd8 (diff)
downloadmate-utils-10d0e538235a3d87c8a5c64193cbcf04c2a8a07b.tar.bz2
mate-utils-10d0e538235a3d87c8a5c64193cbcf04c2a8a07b.tar.xz
mate-disk-usage-analyzer: Memory leak
To detect the memory leak using valgrind: export CFLAGS="-Og -g -fno-omit-frame-pointer -fPIE -pie" export CXXFLAGS="-Og -g -fno-omit-frame-pointer -fPIE -pie" ./autogen.sh --prefix=/usr make clean make sudo make install valgrind --tool=memcheck --undef-value-errors=no --leak-check=full --log-file="report.txt" /usr/bin/mate-disk-usage-analyzer report.txt content: ==16061== 6 bytes in 1 blocks are definitely lost in loss record 174 of 14,390 ==16061== at 0x483880B: malloc (vg_replace_malloc.c:309) ==16061== by 0x56B10D7: g_malloc (gmem.c:99) ==16061== by 0x56CAAEE: g_strdup (gstrfuncs.c:363) ==16061== by 0x56E3743: g_variant_dup_string (gvariant.c:1533) ==16061== by 0x5509DE6: g_settings_get_string (gsettings.c:1795) ==16061== by 0x115664: initialize_charts (baobab.c:1185) ==16061== by 0x11640C: main (baobab.c:1307)
Diffstat (limited to 'logview/logview-manager.c')
0 files changed, 0 insertions, 0 deletions