|
Bugzilla – Full Text Bug Listing |
| Summary: | Timer's default destroy policy not set | ||
|---|---|---|---|
| Product: | ns-3 | Reporter: | Fabian Mauchle <f1mauchl> |
| Component: | core | Assignee: | ns-bugs <ns-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | mathieu.lacage |
| Priority: | P5 | ||
| Version: | ns-3-dev | ||
| Hardware: | All | ||
| OS: | All | ||
| Attachments: | patch | ||
changeset: b1e16a025279 |
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.