effects interrupts may have on code (malloc, sleep, ect..)
 

Maybe someone has had a similar experience with this. I have an application reliable udp library I'm intergrating with some code. I have been getting strange errors that valgrind, gdb, and memcheck have all failed to find (by find I mean overwritten memory, bad allocations, null pointers, ect..) . Im wondering whether setting interrupt handlers on sockets has any effect on other code such as malloc and sleep. I was wondering this because the man page for sleep says to not use alarms and sleep together, which I am.

The errors are random and sometimes generate seg faults and other times bad results.

Try using nanosleep() for interrupt-save sleeps.

Thanks, I'll try this. Im just wondering how sleep and nanosleep differ in implementation , especially in dealing with interrupts.