by piotr5 » Sat Mar 14, 2015 8:47 am
haven't looked at the details, so my view might be unjustified: I'm not sure how your approach actually could work. on one core you allocate space and then free it on another core. does that really work? if there is an allocation-table in shared memory, wouldn't that cause trouble once you communicate through eLink north/south? imho you need to create your own memory-manager. it's suspicious that you are using the command free() and not whatever found in eSDK...