=891= 2,072 bytes in 1 blocks are still reachable in loss record 242 of 246 If gtk is not disabled, you may get notifications of leaks that exist in third-party libraries, such as: =29514= ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2) =29514= For counts of detected and suppressed errors, rerun with: -v =29514= All heap blocks were freed - no leaks are possible =29514= in use at exit: 0 bytes in 0 blocks =29514= Using Valgrind-3.8.1 and LibVEX rerun with -h for copyright info =29514= Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.

=29514= Memcheck, a memory error detector Waf: Leaving directory `/path/to/ns-3-dev/build' Waf: Entering directory `/path/to/ns-3-dev/build'

waf configure -disable-gtk -enable-examples -enable-testsĪn example of clean valgrind output for the 'first' tutorial example is below: To disable gtk (even if it is on your system), provide the '-disable-gtk' option at configure time e.g.: It may be possible to add some suppressions, but it is likely easier to try to disable gtk when you want to use valgrind. In particular, there seems to be a leak in some libraries related to gtk, which is used in ns-3 for the GTK Config Store component. Valgrind for ns-3 is known to work on recent Linux systems that do not have gtk enabled. Valgrind should be used on debug, dynamically linked code (the default in ns-3) and not on statically linked or optimized code see 2.1 Failure to call Simulator::Destroy().

1 Supported platforms and configurations.

Valgrind memcheck in use