> On Thu, 12 Jun 2008 John Tytgat wrote: > In message > alan buckley wrote: > >> I've just been testing GCC4 with the SDL library >> downloaded from the autobuilder packaging site. >> >> It appears that the use of threading is causing >> the test programs to crash. The test programs >> all worked with GCC3. >> >> The SDL threading with RISC OS is just a >> wrapper around pthreads. > > Brr, not good. Is this happening with the static UnixLib runtime > library, or the shared one ? In case of the former (which I suspect > it is as we've haven't made shared libs available via Autobuilder), > this is a showstopper for a release 1 until at least we know the > cause of it.
Sorry, now you've asked I realise I was using the shared UnixLib runtime library. I had forgot to put the -static flag on the command line. The threading program had a different problem after that where the logic meant a pthread_yield was being called during a KILL signal handler. This reports: pthreads: *** fatal error aborting *** pthread_yield called with context switching disabled. Should this really be a fatal error? If it should, is there anyway I can test for context switching being disabled in C code so I can avoid the call to pthread_yield. Regards, Alan _________________________________________________________________ http://clk.atdmt.com/UKM/go/msnnkmgl0010000002ukm/direct/01/ _______________________________________________ GCCSDK mailing list [email protected] Bugzilla: http://www.riscos.info/bugzilla/index.cgi List Info: http://www.riscos.info/mailman/listinfo/gcc Main Page: http://www.riscos.info/index.php/GCCSDK
