Bug 792

Summary:	Neither test.py nor waf --valgrind catch all kinds of memory leaks.
Product:	ns-3	Reporter:	Craig Dowell <craigdo>
Component:	regression	Assignee:	ns-bugs <ns-bugs>
Status:	RESOLVED FIXED
Severity:	blocker	CC:	faker.moatamri
Priority:	P1
Version:	pre-release
Hardware:	All
OS:	All
Attachments:	Patch to fail on memory leaks even if valgrind won't consider them errors.

Description Craig Dowell 2010-01-15 17:34:41 UTC

Currently valgrind doesn't consider some leaks worth reporting as an error no matter how you try to convince it.  We need to look into the valgrind output for ourselves to determine if any memory leak occurred and report an error.

Comment 1 Craig Dowell 2010-01-15 17:37:13 UTC

Created attachment 726 [details]
Patch to fail on memory leaks even if valgrind won't consider them errors.

Patch to update test.py and wutils.py (for waf --valgrind) to call any memory leak an error.

Comment 2 Faker Moatamri 2010-01-19 05:47:39 UTC

Please commit and close the bug, thanks...

Comment 3 Faker Moatamri 2010-01-19 10:59:35 UTC

changeset: aa8364846523