[riot-notifications] [RIOT-OS/RIOT] iotlab-m3: thread tests failing (#10800)

Gaëtan Harter notifications at github.com
Thu Jan 17 15:42:21 CET 2019


So the `thread` tests are not `thread` safe :D as nothing says that when you do `printf` you will not have another `printf` in the middle.

I have two ideas to implement this with  functions`atomic_puts` and `atomic_printf`:

* use a global `mutex` around the original `puts`/`printf`. Which is somehow the same as done for `printk` without the buffer they have: https://en.wikipedia.org/wiki/Printk#Description
* Do it with `irq_disable`
   *  however, the current code does not support it as a special case is only done for `irq_is_in` which does not take into account that interrupts can be disabled. May it also be a similar reason why it did not work for spi ?



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/issues/10800#issuecomment-455195344
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190117/3084b92c/attachment.html>


More information about the notifications mailing list