While running objecteventtest, it was found that valgrind pointed out the
following memory leak:
==13025== 538 (56 direct, 482 indirect) bytes in 1 blocks are definitely lost
in loss record 216 of 226
==13025==at 0x4A06B6F: calloc (vg_replace_malloc.c:593)
==13025==by 0x4C65D8D:
On 01/14/2014 02:10 PM, Nehal J Wani wrote:
While running objecteventtest, it was found that valgrind pointed out the
following memory leak:
==13025== 538 (56 direct, 482 indirect) bytes in 1 blocks are definitely lost
in loss record 216 of 226
==13025==at 0x4A06B6F: calloc
