-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello,
Robert Osfield wrote: > HI Jan, > > Thanks for the further testing and stack trace. > > This is really peculiar - normally one hits threading problems when > one has multi-core systems where race conditions and timing issues are > much more stressed, on single core systems one typically sees few > threading issues in comparison. So... typically if you can get things > running solidly on a multi-core system the single core system will > just work... Yes, that has me puzzled too, but you have to keep in mind that Linux threading is implemented in separate processes. There isn't much difference between a process and a thread on Linux. Even on a single core machine one thread holding a lock could be scheduled away from the CPU while another one is executed. On a multicore machine this only happens sooner. If the multicore system is fast enough to run through the critical section causing the deadlock before the other thread has a chance to acquire the offending lock, you will not see the bug. It is indeed a messy problem to deal with :( > I will boot up my old laptop and get things update and see if it > reproduce any of these problems as my multi-core systems are painfully > rock solid... OK, let me know if you find something out. Jan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org iD8DBQFG0FOfn11XseNj94gRApXnAJ90Rc0SCi2fvFRrirJhPhG2PnX4IACcDRtr TNzirC7ThbO3ZKSGdT+jJgw= =9yZR -----END PGP SIGNATURE----- _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
