Bug 792 – Neither test.py nor waf --valgrind catch all kinds of memory leaks.

Bug 792 - Neither test.py nor waf --valgrind catch all kinds of memory leaks.


Summary:	Neither test.py nor waf --valgrind catch all kinds of memory leaks.

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	regression
Version:	pre-release
Hardware:	All All

Importance:	P1 blocker
Assigned To:	ns-bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-01-15 17:34 UTC by Craig Dowell
Modified:	2010-01-19 10:59 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
Patch to fail on memory leaks even if valgrind won't consider them errors. (3.02 KB, patch) 2010-01-15 17:37 UTC, Craig Dowell	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

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