GNOME Bugzilla – Bug 167421
crash after one is trying to play
Last modified: 2012-02-16 00:03:50 UTC
Distribution: Debian 3.1 Package: gnome-games Severity: normal Version: GNOME2.8.1 2.8.2 Gnome-Distributor: Debian Synopsis: crach after one is trying to play Bugzilla-Product: gnome-games Bugzilla-Component: gnect Bugzilla-Version: 2.8.2 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/games/gnect' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 1265)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x70fafb58 in waitpid () from /lib/libpthread.so.0
+ Trace 55713
Thread 1 (Thread 16384 (LWP 1265))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-02-14 19:26 ------- Unknown version 2.8.2 in product gnome-games. Setting version to "2.8.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-games". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was kevin.agbakpem@gmail.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Thanks for the bug report. The stack trace matches the one in bug 154480, but it was claimed that the bug was fixed in the 2.7.x series whereas this is filed against 2.8.2...
And it doesn't look like a 64-bit machine either. Interesting, worrying too.
Hrm... My call on 154480 was based on the fact it was a crash in AI and anything platform that used a long of 64 bits would crash because of a bad cast much earlier on in the AI, iirc leading to several possible crashes. It probably wouldn't hurt to move the AI over to glib, or (pipe dream) remove the opening book altogether. kevin.agbakpem@gmail.com: Could you perhaps tell us often it crashes for you... try setting Level 3 vs Level 3. If you could run gnect from console and spot any error message, that would also be great.
I have had gnect running overnight playing itself (at a variety of different level combinations) on an x86. No crashes yet, but there are some scenarios I haven't tried yet.
Copied fom Bug #154480: ----------------- Steps to reproduce the crash: 1. Fire up gnect on a sparc64 running GNU/Linux 2. Start a new game 3. play one stone. Wait for the computer opponent to play a stone, which will produce a segfault. -----------------
I was not able to reproduce this either. CPU is 32Bit AMD Athlon. Debian Gnome, matching gnect version. Callum are you sure this is a 64Bit CPU?
Err I meant *no* 64Bit CPU. The related bugs were on 64Bit machines.
I was basing my 32-bit comment on the fact that the address space was 32-bit. I've just checked the sparc64 version and it is too, so, no I'm not sure that it isn't a 64-bit machine. However, it is definitely 2.8, which is *after* the 64-bit fix. I have narrowed the problem down to one of three things: - bin_compare still crashes (and the compiler has done something funky to get rid of the stack frame). - fast_check_node crashes (ditto for compiler tricks) - backtrace gets a bad value, I'm pretty certain all the other indices are contrained by for loops and the like to be correct (but not absolutely certain).
Closing due to age, assuming not present anymore.