During the course of debugging a simple xeno-native app, I notice some of the return codes for heap functions are at odds with the documentation.. For example rt_heap_bind() when used with TM_NONBLOCK returns -EAGAIN where as the docs would suggest -EWOULDBLOCK should be returned.
Also noted that rt_heap_delete() returns -EBUSY if another task holds a valid heap descriptor - Undocumented, but well worth having as it can be used to prevent the RT_HEAP memory from disappearing (either by a module unloading, or user space app terminating). Are these return codes likely to change in the forseeable future ? Regards, Paul. _______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
