GNOME Bugzilla – Bug 154480
segfault on SPARC
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian 3.1 Package: gnome-games Severity: normal Version: GNOME2.6.1 2.6.2 Gnome-Distributor: Debian Synopsis: segfault on SPARC Bugzilla-Product: gnome-games Bugzilla-Component: gnect Bugzilla-Version: 2.6.2 BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash:gnect crashes pretty soon on SPARC 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. Expected Results: It should Just Work(TM) How often does this happen? every time 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)...[Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 6318)] (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)...(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)...0x7031fb58 in waitpid () from /lib/libpthread.so.0
+ Trace 50755
Thread 1 (Thread 16384 (LWP 6318))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-10-04 12:38 ------- Unknown version 2.6.2 in product gnome-games. Setting version to "1.4.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 wouter@grep.be. 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.
unique stack trace.
Not really... This is a duplicate of bug #140545 trying to trick bughunters it is unique. It was only a problem on certain (64-bit) CPUs, fixed during the 2.7.0 cycle.
Yeah, I agree, it looks like a duplicate. gnome-games 2.8.0 compiles in a GNOME 2.6 environment so you don't need to upgrade everything to get a fix. *** This bug has been marked as a duplicate of 140545 ***
Damn. Do we need to worry about stealth bugs now ? :-)