[Ns-bugs] [Bug 305] New: Tracing asserts too easily now

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

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

           Summary: Tracing asserts too easily now
           Product: ns-3
           Version: pre-release
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: simulation core
        AssignedTo: ns-bugs at isi.edu
        ReportedBy: gjcarneiro at gmail.com


With this simple tracing code:
http://code.nsnam.org/gjc/ns-3-pyviz/rev/6eccb090137c

This happens:

Incompatible types. (feed to "c++filt -t")
got=N3ns318MemPtrCallbackImplIPNS_5PyVizEMS1_FvSsNS_3PtrIKNS_6PacketEEENS_12Mac48AddressEEvSsS6_S7_NS_5emptyESA_SA_EE,
expected=PN3ns312CallbackImplIvSsNS_3PtrIKNS_6PacketEEENS_5emptyES5_S5_S5_EE
Command ['/usr/bin/python', 'examples/mixed-wireless.py'] exited with code -11 

It turns out that CsmaNetDevice and WifiNetDevice have different Tx/Rx trace
event signatures:

wifi:   TracedCallback<Ptr<const Packet>, Mac48Address> m_rxLogger;
csma:   TracedCallback<Ptr<const Packet> > m_rxTrace;

The code asserted when connecting on a csma netdevice, which has a different
signature.

Why they have different signatures is another problem.  Right now I am
concerned about why TraceConnect asserts.  Why does this common use case of
catching every transmission have to be so damn hard in NS-3? :-(

Thoughts?


-- 
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.