[Ns-developers] ns-3 valgrind issue
lentracy at u.washington.edu
Tue Aug 10 15:12:35 PDT 2010
I got the same errors after install of newer Ubuntu awhile back. I'm
interested to know the source as well :).
I think I saw this lost 120 bytes for every test I ran.
On Tue, Aug 10, 2010 at 2:08 PM, Josh Pelkey <jpelkey at gatech.edu> wrote:
> Hi all,
> Does anyone know why I am getting valgrind failures in test.py, even
> though I know that most of these tests pass? Perhaps it is my version
> of valgrind (3.5.0)? This is what it is showing for most test cases:
> ==7121== 120 bytes in 1 blocks are definitely lost in loss record 1 of 1
> ==7121== at 0x4C25153: malloc (vg_replace_malloc.c:195)
> ==7121== by 0xA4F5F18: getdelim (iogetdelim.c:68)
> ==7121== by 0xC602322: ??? (in /lib/libselinux.so.1)
> ==7121== by 0xC60A8D5: ??? (in /lib/libselinux.so.1)
> ==7121== by 0xC5FA2AA: ??? (in /lib/libselinux.so.1)
> ==7121== by 0x7FF0003B7: ???
> ==7121== by 0x65722F79656B6C64: ???
> ==7121== by 0x332D736E2F736F6F: ???
> ==7121== by 0x6E6F6E696C6C612C: ???
> ==7121== by 0x642D332D736E2F64: ???
> ==7121== by 0x646C6975622F7664: ???
> ==7121== by 0x752F67756265642E: ???
> ==7121== LEAK SUMMARY:
> ==7121== definitely lost: 120 bytes in 1 blocks
> ==7121== indirectly lost: 0 bytes in 0 blocks
> ==7121== possibly lost: 0 bytes in 0 blocks
> ==7121== still reachable: 0 bytes in 0 blocks
> ==7121== suppressed: 0 bytes in 0 blocks
> Thanks for any help.
> Josh Pelkey
More information about the Ns-developers