[Ns-bugs] [Bug 1358] New: PacketMetadata::~PacketMetadata() writes in freed memory
code@nsnam.ece.gatech.edu
code at nsnam.ece.gatech.edu
Sun Feb 5 10:15:50 PST 2012
https://www.nsnam.org/bugzilla/show_bug.cgi?id=1358
Summary: PacketMetadata::~PacketMetadata() writes in freed
memory
Product: ns-3
Version: ns-3-dev
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
Component: network
AssignedTo: ns-bugs at isi.edu
ReportedBy: nbaldo at cttc.es
Estimated Hours: 0.0
Created attachment 1327
--> https://www.nsnam.org/bugzilla/attachment.cgi?id=1327
valgrind error log
I am experiencing corrupted memory errors in a program when executed with
around 90000 nodes or more. The symptoms (which vary a bit depending on the
exact number of nodes) are sementation faults or failed assertions in malloc.c,
which point to a memory corruption problem. With smaller number of nodes, the
problem is not evident.
I've traced the problem to a write operation in a block of already freed memory
performed by PacketMetadata::~PacketMetadata(). Please have a look at the
attached valgrind log.
I've been able to reproduce this bug only with the LENA code, in particular the
attached log was produced with changeset 7542c79c9d19 which is available at
http://code.nsnam.org/nbaldo/ns-3-lena-dev/
Note that this code is pretty much up-to-date with respect to ns-3-dev (the
last merged changeset is 90904c14135f of January 29, 2012)
Here is the command line used to reproduce the error:
./waf --run lena-rem-sector-antenna --command="%s
--ns3::RadioEnvironmentMapHelper::XRes=300
--ns3::RadioEnvironmentMapHelper::YRes=300"
I have a very poor understanding of the inner working of the fancy memory
management solution of PacketMetadata, hence any suggestion to get to a fix
would be very much appreciated.
--
Configure bugmail: https://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Ns-bugs
mailing list