Communication protocol handler for the taskrambler framework. This does not contain specific protocol implementations but the abstract code to handle them.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 

68 lines
3.3 KiB

==25008== Memcheck, a memory error detector
==25008== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==25008== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info
==25008== Command: ./testserver
==25008==
==25008== Conditional jump or move depends on uninitialised value(s)
==25008== at 0x4017A74: index (strchr.S:77)
==25008== by 0x400743D: expand_dynamic_string_token (dl-load.c:425)
==25008== by 0x400802D: _dl_map_object (dl-load.c:2302)
==25008== by 0x400138D: map_doit (rtld.c:626)
==25008== by 0x400E993: _dl_catch_error (dl-error.c:187)
==25008== by 0x4000B30: do_preload (rtld.c:815)
==25008== by 0x4004122: dl_main (rtld.c:1632)
==25008== by 0x401533B: _dl_sysdep_start (dl-sysdep.c:249)
==25008== by 0x4004A4C: _dl_start (rtld.c:331)
==25008== by 0x40011A7: ??? (in /lib64/ld-2.19.so)
==25008==
==25008==
==25008== HEAP SUMMARY:
==25008== in use at exit: 1,024 bytes in 4 blocks
==25008== total heap usage: 12,272 allocs, 12,268 frees, 1,601,216 bytes allocated
==25008==
==25008== 256 bytes in 1 blocks are definitely lost in loss record 1 of 4
==25008== at 0x4C28730: malloc (vg_replace_malloc.c:291)
==25008== by 0x4E3497C: newElement (memory.c:82)
==25008== by 0x4E34B19: TR_malloc (memory.c:442)
==25008== by 0x4E34B50: TR_calloc (memory.c:460)
==25008== by 0x4E35144: TR_classNewv (i_class.c:55)
==25008== by 0x4E3532E: TR_classNew (i_class.c:81)
==25008== by 0x4018DA: main (testserver.c:123)
==25008==
==25008== 256 bytes in 1 blocks are definitely lost in loss record 2 of 4
==25008== at 0x4C28730: malloc (vg_replace_malloc.c:291)
==25008== by 0x4E3497C: newElement (memory.c:82)
==25008== by 0x4E34B19: TR_malloc (memory.c:442)
==25008== by 0x4E34B50: TR_calloc (memory.c:460)
==25008== by 0x4E35144: TR_classNewv (i_class.c:55)
==25008== by 0x4E3532E: TR_classNew (i_class.c:81)
==25008== by 0x4018F2: main (testserver.c:124)
==25008==
==25008== 256 bytes in 1 blocks are definitely lost in loss record 3 of 4
==25008== at 0x4C28730: malloc (vg_replace_malloc.c:291)
==25008== by 0x4E3497C: newElement (memory.c:82)
==25008== by 0x4E34B19: TR_malloc (memory.c:442)
==25008== by 0x4E34B50: TR_calloc (memory.c:460)
==25008== by 0x4E35144: TR_classNewv (i_class.c:55)
==25008== by 0x4E3532E: TR_classNew (i_class.c:81)
==25008== by 0x40190A: main (testserver.c:125)
==25008==
==25008== 256 bytes in 1 blocks are definitely lost in loss record 4 of 4
==25008== at 0x4C28730: malloc (vg_replace_malloc.c:291)
==25008== by 0x4E3497C: newElement (memory.c:82)
==25008== by 0x4E34B19: TR_malloc (memory.c:442)
==25008== by 0x4E34B50: TR_calloc (memory.c:460)
==25008== by 0x4E35144: TR_classNewv (i_class.c:55)
==25008== by 0x4E3532E: TR_classNew (i_class.c:81)
==25008== by 0x401920: main (testserver.c:126)
==25008==
==25008== LEAK SUMMARY:
==25008== definitely lost: 1,024 bytes in 4 blocks
==25008== indirectly lost: 0 bytes in 0 blocks
==25008== possibly lost: 0 bytes in 0 blocks
==25008== still reachable: 0 bytes in 0 blocks
==25008== suppressed: 0 bytes in 0 blocks
==25008==
==25008== For counts of detected and suppressed errors, rerun with: -v
==25008== Use --track-origins=yes to see where uninitialised values come from
==25008== ERROR SUMMARY: 5 errors from 5 contexts (suppressed: 0 from 0)