> > > The crashing bug at startup is very difficult to track down. > > > > Is there something I could do ? Don't know, like running the debug > > executable > > under gdb to provide you some infos on how/where it crashes ? Which commands > > should I enter ? (I've never used gdb) > > > > Not really, I can see where it crashes, more or less. It has to do > with closing of the threads and something calling mutex'es, which > makes sure that the threads don't alter and access the some data > simultaneously. But what exactly causes the crash I don't understand.
Don't know if that can help but ... yesterday I reinstalled everything on my new home PC (Vista Home Premium) and recompiled the latest code. Now the glib thread version no longer crashes at startup, I can even play, analyse etc. But as soon as I change the number of threads it crashes (immediately after entrering the number). Otherwise, with the win threads (Core2Duo 2.13GHz): 1 thread ==> 41K eval/s 2 threads ==> 82K eval/s :)) MaX.
_______________________________________________ Bug-gnubg mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnubg
