AnsweredAssumed Answered

mcc_recv_nocopy never timeouts

Question asked by Petr Kubiznak on Feb 27, 2014
Latest reply on Mar 18, 2014 by alejandrolozano

I think I hit on a bug in implementation of blocking calls in MCC library. I'm using mcc_recv_nocopy() with finite non-zero timeout to receive a message from Linux (A5) to MQX (M4) on Vybrid. It works fine if the system time is not changed, but when I change it using the following code, subsequent calls to mcc_recv_nocopy() never return until a message is received (which may never happen).



Am I misusing something or is this a bug? Is there any patch? It is pretty important to me.

(I'm not even asking what would happen if I changed the system time between a call to mcc_recv_nocopy() and its return.)