I think no.
Well you're entitled to think whatever you want. If a minor program, which has a few millisecs of life time, has some low possibility of chrash:
Except since you're using threads, not processes, the data used by the forked tread is the same data that's used by the main process, thus corruption in onw, will spill over into the other. And this module uses os native functions, whose that the os os uses for all the programs.
It has nothing to do with kernel threads or user threads, but to do with simultaneously reading and/or writting to/from the same memory (an undefined operation), known as the critical section of a program. On Linux i don't see apps crashing very often.
THat's because on Linux, most multi-threaded programs are reentrant/thread safe and implement a synchronization scheme to prevent critical sections from being executed simultaneously. And with BMax is perfectly possible to use threads.
I didn't say it wasn't possible, I said it wasn't safe! PS: it perfectly works on Linux to mee too.
Well on a single CPU computer the chance of two critical sections being executed simultaneously is very slim, so most of the times it will work fine. Ofcourse in a multiple processor environment, the risk goes up exponentially as the number of CPUs increase linearly.But hey, if you want to send a robot into production with potentially fatal flaws in its programming, that's your funeral.