On Friday 28 September 2001 00:10, Estabridis, Janet P wrote: [...] > 3. But, the real weird thing about this code now is that I added some > new code to do some coordinate translations (the final piece of code) > and the statement that crashes the code is assigning a double value > that I have just finished calculating locally into a double variable in > the old style shared memory so that a user space program can print it > out since the kernel does not support the printing of floats in kernel > space.
Well, I don't know if it has much to do with your problems, but keep in mind that floating point and shared memory (or any multithreaded or ISR setup where different threads of execution share floating point values) is dangerous. Depending on your hardware, double writes (64 bit) may not be atomic - and floating point values are very sensitive to corrption! However, it's the *reader* that gets an FP exception if synchronization fails - not the writer... //David Olofson --- Programmer, Reologica Instruments AB .- M A I A -------------------------------------------------. | Multimedia Application Integration Architecture | | A Free/Open Source Plugin API for Professional Multimedia | `----------------------------> http://www.linuxdj.com/maia -' .- David Olofson -------------------------------------------. | Audio Hacker - Open Source Advocate - Singer - Songwriter | `-------------------------------------> http://olofson.net -' -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED] -- For more information on Real-Time Linux see: http://www.rtlinux.org/
