|
Bugzilla – Full Text Bug Listing |
| Summary: | Valgrind detects memory leaks from Click when using ns-3-click | ||
|---|---|---|---|
| Product: | ns-3 | Reporter: | Lalith Suresh <suresh.lalith> |
| Component: | click | Assignee: | Ruben Merz <ruben> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ns-bugs, suresh.lalith |
| Priority: | P5 | ||
| Version: | pre-release | ||
| Hardware: | All | ||
| OS: | All | ||
| Attachments: | Ipv4ClickRouting patch | ||
Partially fixed in changesets 7691:63e7bd888869 and 7690:6079432abbae. Seems like the rest of the leaks originate from within Click and is confusing valgrind, so I'm closing this now. |
Created attachment 1149 [details] Ipv4ClickRouting patch Seems like valgrind is complaining about the memory that Click allocates for its elements and other components which are not essentially meant to be deallocated by Click (i.e, they're cleaned up automatically by the OS when the click process terminates). This can be seen by running: $: ./waf --run nsclick-simple-lan --command-template="valgrind --leak-check=full --show-reachable=yes %s" I've attached a patch to Ipv4ClickRouting which helps get rid of a few of the complaints.