I have a Resource Manager that manages LEDs.  LEDs are just IO, turn on and off with in32 out32.
the resmgr, turns LED on, off, or blink at one of two different rates.
If we run a system simulation, the LED resource manager will core dump after a few hours.

If you look at the core dump thru gdb it shows:
#0 0x00101178 in in32 (__addr=4294967295)
     at c:/QNX650/target/qnx6/usr/include/arm/inout.h:78

the address shown in gdb is 0xFFFFFFFF, however when I call in32, the address it sends are all constants in code (#
define LED_ADDR....)

how can it be getting an address of 0xFFFFFFFF?  

Could it be an issue with an interrupt happening during the call to in32 and when it returns from interrupt the address 
is wrong?  
Do I need some protection against that happening?