For some reason, when calling malloc(), the return is always null. I confirmed this with a step through of the function.
The solution is going to be to replace all malloc calls with arrays, and just forget about destroying arrays. This should be fine for now - malloc is only used for the queue implementation, but there is no real reason to be destroying queues in the current firmware 2.0 implementation.
For some reason, when calling malloc(), the return is always null. I confirmed this with a step through of the function.
The solution is going to be to replace all malloc calls with arrays, and just forget about destroying arrays. This should be fine for now - malloc is only used for the queue implementation, but there is no real reason to be destroying queues in the current firmware 2.0 implementation.