[Ns-bugs] [Bug 248] Newer version of tcp-2way that exhibits an 'excess bytes' problem

[bugzilla-daemon@nsnam-www.ece.gatech.edu]

http://www.nsnam.org/bugzilla/show_bug.cgi?id=248





------- Comment #5 from raj.b at gatech.edu  2008-07-08 11:28 -------
I believe I'm not even getting to the erroneous point, but getting crasher
before even getting to this point (using today's ns-3-dev):
./tcp-2way-2 --useDummyBytes=0 --recvSize=600 --preSchedule=1 --useBadTimings=0
tcpip_configure_pt2pt_channel(0,600,)
Prescheduling Packets.
ScheduleNexttime=0,tag=A,size=0
ScheduleNexttime=0.04,tag=B,size=0
ScheduleNexttime=0.08,tag=C,size=10
ScheduleNexttime=0.12,tag=D,size=10
ScheduleNexttime=0.16,tag=E,size=100
ScheduleNexttime=0.2,tag=F,size=100
ScheduleNexttime=0.24,tag=G,size=1000
ScheduleNexttime=0.28,tag=H,size=1000
ScheduleNexttime=0.32,tag=I,size=10000
ScheduleNexttime=0.36,tag=J,size=10000
subsequent ScheduleNext() REUSING time 0.36
ScheduleNext() returns false
Before Marking|
assert failed. file=/home/raj/code.nsnam.org/ns-3-dev/build/debug/ns3/buffer.h,
line=546, cond="Check (m_current)"
Trace/breakpoint trap

In gdb:
Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 0xb6cc4720 (LWP 23707)]
ns3::Buffer::Iterator::WriteU8 (this=0xbf891e54, data=0 '\0') at
/home/raj/code.nsnam.org/ns-3-dev/build/debug/ns3/buffer.h:548
548       if (m_current < m_zeroStart)
(gdb) bt
#0  ns3::Buffer::Iterator::WriteU8 (this=0xbf891e54, data=0 '\0') at
/home/raj/code.nsnam.org/ns-3-dev/build/debug/ns3/buffer.h:548
#1  0xb7b93ed7 in ns3::Buffer::Iterator::WriteU64 (this=0xbf891e54, data=0) at
../src/common/buffer.cc:802
#2  0x0805e7bb in ns3::ArchHeader::Serialize (this=0xbf892068, i=
      {m_zeroStart = 17, m_zeroEnd = 17, m_dataStart = 0, m_dataEnd = 17,
m_current = 18, m_data = 0x808a9b0 ""}) at tcp-2way-2.cc:330
#3  0xb7bc6348 in ns3::Packet::AddHeader (this=0x808a968, header=@0xbf892068)
at ../src/common/packet.cc:190
#4  0x0805bc88 in ns3::TalkerApp::DoSendPacket (this=0x8089240,
sock=@0xbf892178, fill=65 'A', payloadsize=0, msgid=0, src=0, dest=0)
    at tcp-2way-2.cc:509
#5  0x0805c1e5 in ns3::TxTalkerApp::SendPacket (this=0x8089240, fill=65 'A',
payloadsize=0, msgid=0, src=0, dest=0)
    at tcp-2way-2.cc:964
#6  0x08056d0b in Notify (this=0x80894c0) at
/home/raj/code.nsnam.org/ns-3-dev/build/debug/ns3/simulator.h:813
#7  0xb7b67186 in ns3::EventImpl::Invoke (this=0x80894c0) at
../src/simulator/event-impl.cc:39
#8  0xb7b6e909 in ns3::SimulatorPrivate::ProcessOneEvent (this=0x8087098) at
../src/simulator/simulator.cc:207
#9  0xb7b6e95b in ns3::SimulatorPrivate::Run (this=0x8087098) at
../src/simulator/simulator.cc:235
#10 0xb7b71286 in ns3::Simulator::Run () at ../src/simulator/simulator.cc:480
#11 0x0805f89c in main (argc=5, argv=0xbf892484) at tcp-2way-2.cc:1305

This looks to be a bug in the ArchHeader code that's blocking investigation of
the actual issue.  Can you specify a revision number of ns-3-dev which exhibits
the issue?


-- 
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.