valgrind output - 'ae' daemon, filemon, filedescriptormon, selfmon, socketmon, procmon running

[GoogleCodeExporter]

============  start here  ===========
constructMonResponse: [:10:1354245304696760-1046:11:AE:]
==6388== Syscall param set_robust_list(head) points to uninitialised byte(s)
==6388==    at 0x8197E62: _dl_sysinfo_int80 (in 
/home/ravi/nu/as/proj/trunk/src/ae/bin/ae)
==6388==    by 0x8158C60: _IO_proc_open (in 
/home/ravi/nu/as/proj/trunk/src/ae/bin/ae)
==6388==    by 0x109: ???
==6388==  Address 0x8a7e8b8 is not stack'd, malloc'd or (recently) free'd
==6388== 
from Android-SSL: [:10:1354236249742000-1:00:AM:]
============================

========  start here  ===========
processMonitorMsg: stored msg: 
=[:10:1354245382687855-863:22:PM:0003:11:A1:myproc2_myproc2 -a_logmsg:]
constructMonResponse: [:10:1354245382687855-863:11:AE:]
monitor-manager: data from: filedescr = [:10:1354245384733505-1062:00:FD:], 
numMsg = 3766 
constructMonResponse: [:10:1354245384733505-1062:11:AE:]
==6679== Syscall param set_robust_list(head) points to uninitialised byte(s)
==6679==    at 0x8197E62: _dl_sysinfo_int80 (in 
/home/ravi/nu/as/proj/trunk/src/ae/bin/ae)
==6679==    by 0x8158C60: _IO_proc_open (in 
/home/ravi/nu/as/proj/trunk/src/ae/bin/ae)
==6679==    by 0x10D: ???
==6679==  Address 0x8a7e8b8 is not stack'd, malloc'd or (recently) free'd
==6679== 
monitor-manager: data from: filemon = 
[:10:1354245385738013-529:00:FM:003:11:A1:filemon_chksum_error:], numMsg = 3767 
=========================================

Original issue reported on code.google.com by ravt...@gmail.com on 30 Nov 2012 at 3:18

[GoogleCodeExporter]

Vlgrind results (ran for 17+ hours, received 43264 messages from monitors and 
sent them to Android AeManager
===========================================================

==19465== 
==19465== HEAP SUMMARY:
==19465==     in use at exit: 0 bytes in 0 blocks
==19465==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==19465== 
==19465== All heap blocks were freed -- no leaks are possible
==19465== 
==19465== For counts of detected and suppressed errors, rerun with: -v
==19465== Use --track-origins=yes to see where uninitialised values come from
==19465== ERROR SUMMARY: 1687443 errors from 287 contexts (suppressed: 0 from 0)
==19468== 
==19468== HEAP SUMMARY:
==19468==     in use at exit: 0 bytes in 0 blocks
==19468==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==19468== 
==19468== All heap blocks were freed -- no leaks are possible
==19468== 
==19468== For counts of detected and suppressed errors, rerun with: -v
==19468== Use --track-origins=yes to see where uninitialised values come from
==19468== ERROR SUMMARY: 44526 errors from 246 contexts (suppressed: 0 from 0)
ravi@ravi-ubuntu12-04:~/nu/as/proj/trunk/src/ae/bin$ ==19492== 
==19492== HEAP SUMMARY:
==19492==     in use at exit: 0 bytes in 0 blocks
==19492==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==19492== 
==19492== All heap blocks were freed -- no leaks are possible
==19492== 
==19492== For counts of detected and suppressed errors, rerun with: -v
==19492== Use --track-origins=yes to see where uninitialised values come from
==19492== ERROR SUMMARY: 184494 errors from 293 contexts (suppressed: 0 from 0)
==19492== could not unlink /tmp/vgdb-pipe-from-vgdb-to-19492-by-root-on-???
==19492== could not unlink /tmp/vgdb-pipe-to-vgdb-from-19492-by-root-on-???
==19492== could not unlink /tmp/vgdb-pipe-shared-mem-vgdb-19492-by-root-on-???
==19491== 
==19491== HEAP SUMMARY:
==19491==     in use at exit: 0 bytes in 0 blocks
==19491==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==19491== 
==19491== All heap blocks were freed -- no leaks are possible
==19491== 

Original comment by ravt...@gmail.com on 30 Nov 2012 at 6:47

[GoogleCodeExporter]

Closing this as the daemon and monitors works without memory leaks or coredump; 
but will fuzz with resources again to simulate to test how robust the 
components are,
ravi.

Original comment by ravt...@gmail.com on 1 Dec 2012 at 2:36

• Changed state: Fixed

[GoogleCodeExporter]

Verified with unit testing

Original comment by tbrt....@gmail.com on 9 Dec 2012 at 9:24

• Changed state: Verified