|
Bugzilla – Full Text Bug Listing |
| Summary: | valgrind error in test suite ipv6-dual-stack | ||
|---|---|---|---|
| Product: | ns-3 | Reporter: | Tom Henderson <tomh> |
| Component: | ipv6 | Assignee: | Tommaso Pecorella <tommaso.pecorella> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ns-bugs |
| Priority: | P5 | ||
| Version: | pre-release | ||
| Hardware: | All | ||
| OS: | All | ||
| Attachments: |
Callback nullified on socket.cc
Nullify some (maybe) relevant callbacks. The memory leak and some quite nasty silent ones. |
||
|
Description
Tom Henderson
2012-02-25 11:27:59 UTC
Created attachment 1340 [details]
Callback nullified on socket.cc
Doesn't seems to be related to IPv6 specifically, but to a generic Callback not nullified properly (again).
Can you try this patch ?
Thanks,
T.
Created attachment 1341 [details]
Nullify some (maybe) relevant callbacks.
Nullified more Callbacks, also on IPv4
(In reply to comment #2) > Created attachment 1341 [details] > Nullify some (maybe) relevant callbacks. > > Nullified more Callbacks, also on IPv4 Neither this nor the more general idea of putting Nullify in the Callback destructor fixed the issue. (In reply to comment #3) > (In reply to comment #2) > > Created attachment 1341 [details] > > Nullify some (maybe) relevant callbacks. > > > > Nullified more Callbacks, also on IPv4 > > Neither this nor the more general idea of putting Nullify in the Callback > destructor fixed the issue. I think I have an idea about what's the problem. It would be interesting to test it on Udp sockets, if they could do a connect ... :) Anyway, it's about the fact that a TCP socket shouldn't "bind" to both IPv4 *and* IPv6, but if they do bind on IPv6 they can still receive "pseudo-IPv4" connections. That's disturbing. I'll try to scavenge more the thing. Dual stack nodes should be forbidden (in general, not only in ns-3). T. Created attachment 1342 [details]
The memory leak and some quite nasty silent ones.
Vittu !
DoTeardown should ALWAYS call Simulator::Destroy();
So dramatically stupid that I didn't check it.
On the other hand, another case of serendipity. I found number of hidden bugs that were just lurking in the dark. Check the patch please.
(In reply to comment #5) > Created attachment 1342 [details] > The memory leak and some quite nasty silent ones. > > Vittu ! > > DoTeardown should ALWAYS call Simulator::Destroy(); > > So dramatically stupid that I didn't check it. > > On the other hand, another case of serendipity. I found number of hidden bugs > that were just lurking in the dark. Check the patch please. looks ok to me Fixed: changeset 7747 - 53a26ce38807 |