That one could be due to freeprocess trying to flush or close an io pipe.
There was an OSX fix for freeprocess a while ago that may be worth looking into for linux. I blamed 4.x pthreading when FLTK was displaying the same behavior and decided gcc3.3 was a winner.
Are you using 3.3 or 4.x toolchain?
There was an OSX fix for freeprocess a while ago that may be worth looking into for linux. I blamed 4.x pthreading when FLTK was displaying the same behavior and decided gcc3.3 was a winner.
Are you using 3.3 or 4.x toolchain?