AnsweredAssumed Answered

Sending ethernet messages to 2 destinations faults code...

Question asked by rick stuart on Jan 17, 2015
Latest reply on Feb 3, 2015 by Radek Sestak



When I am sending Ethernet messages to 2 destinations, I am fairly sure that I am un-allocating (freeing up) the memory containing the Ethernet message twice.  And this is causing the code to stop working.  Unfortunately, the code that frees up the memory is buried deep into the MQX code.  Not in my application.  I would rather not touch the MQX code if possible.  Is there a known way to prevent the (I think) "RTCSPCB_free_internal(PCB_PTR)" function from freeing up the memory on the first go-around and not on the second? 

Reading the code hints that I might make use of a "duplication" concept.  But I am not familiar with this feature and do not understand the real purpose of this feature.  So I am hesitant on using it.