Menu

#77 DVBstreamer-1.2 memory check

open
nobody
None
5
2011-02-22
2011-02-22
No

DVBStreamer debug procedure with memory leak check using the VALGRIND tool.

It has been collected the two kinds of logs, the summarized logs and full logs using verbose mode of Valgrind:

+ setup procedure log
+ dvbstreamer logs
+ dvbctrl logs

Discussion

  • Mauro L. Filho

    Mauro L. Filho - 2011-02-22

    Valgrind check logs

     
  • Mauro L. Filho

    Mauro L. Filho - 2011-02-22

    For more information about this test, there is a README file at the path dvbstreamer-1.2.valgrind\1.2\01_test\

     
  • Mauro L. Filho

    Mauro L. Filho - 2011-02-22

    For more information about this test, there is a README file at the path dvbstreamer-1.2.valgrind\1.2\01_test\
    This REAME file explain the every log condition.

     
  • Mauro L. Filho

    Mauro L. Filho - 2011-02-22

    I've choose an especific summary log, catched after start the DVBstreamer and then quit.
    I found the following information:

    ==17507== Memcheck, a memory error detector
    ==17507== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
    ==17507== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for copyright info
    ==17507== Command: dvbstreamer -a 0
    ==17507==
    ==17507== Syscall param ioctl(generic) points to uninitialised byte(s)
    ==17507== at 0x421BC14: ioctl (syscall-template.S:82)
    ==17507== by 0x806095F: DVBInit (dvb.c:138)
    ==17507== by 0x805EE15: main (main.c:275)
    ==17507== Address 0xbe8e3502 is on thread 1's stack
    ==17507==
    ==17507==
    ==17507== HEAP SUMMARY:
    ==17507== in use at exit: 64,502 bytes in 201 blocks
    ==17507== total heap usage: 1,757 allocs, 1,556 frees, 553,865 bytes allocated
    ==17507==
    ==17507== LEAK SUMMARY:
    ==17507== definitely lost: 4 bytes in 1 blocks
    ==17507== indirectly lost: 0 bytes in 0 blocks
    ==17507== possibly lost: 0 bytes in 0 blocks
    ==17507== still reachable: 64,498 bytes in 200 blocks
    ==17507== suppressed: 0 bytes in 0 blocks
    ==17507== Rerun with --leak-check=full to see details of leaked memory
    ==17507==
    ==17507== For counts of detected and suppressed errors, rerun with: -v
    ==17507== Use --track-origins=yes to see where uninitialised values come from
    ==17507== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 54 from 9)

     

Log in to post a comment.

Monday.com Logo