Bug 568 – Timer's default destroy policy not set

Bug 568 - Timer's default destroy policy not set


Summary:	Timer's default destroy policy not set

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	core
Version:	ns-3-dev
Hardware:	All All

Importance:	P5 major
Assigned To:	ns-bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-05-18 09:00 UTC by Fabian Mauchle
Modified:	2009-05-19 09:41 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
patch (335 bytes, patch) 2009-05-18 09:00 UTC, Fabian Mauchle	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 Fabian Mauchle 2009-05-18 09:00:27 UTC

Created attachment 440 [details]
patch

The default destroy policy of a Timer constructed with the default constructor, does not set the destroy policy to CHECK_ON_DESTROY as stated in the documentation.

Because of this, during destruction, it is not checked whether the event is still active (scheduled), which can cause illegal memory access when the event is executed later.

Comment 1 Mathieu Lacage 2009-05-19 09:41:22 UTC

changeset: b1e16a025279