GNOME Bugzilla – Bug 377226
crash in Help: Just launched the Mines ...
Last modified: 2006-11-20 19:09:09 UTC
Version: 2.16.1 What were you doing when the application crashed? Just launched the Mines Manual from the Mines (Gnome game) help menu. Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.17.2 2006-11-14 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 104136704 vsize: 0 resident: 104136704 share: 0 rss: 40689664 rss_rlim: 0 CPU usage: start_time: 1163982989 rtime: 0 utime: 138 stime: 0 cutime:120 cstime: 0 timeout: 18 it_real_value: 0 frequency: 2 Backtrace was generated from '/usr/bin/yelp' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1228212528 (LWP 2863)] [New Thread -1285555312 (LWP 2891)] [New Thread -1275790448 (LWP 2887)] [New Thread -1267324016 (LWP 2884)] [New Thread -1247876208 (LWP 2883)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 87851
Thread 1 (Thread -1228212528 (LWP 2863))
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Following is the backtrace after installing "yelp-dbgsym". If there are any other debug packages that you need me to install, let me know exactly which ones. Thanks, Justin Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.17.2 2006-11-14 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 100192256 vsize: 0 resident: 100192256 share: 0 rss: 41648128 rss_rlim: 0 CPU usage: start_time: 1164038972 rtime: 0 utime: 168 stime: 0 cutime:152 cstime: 0 timeout: 16 it_real_value: 0 frequency: 2 Backtrace was generated from '/usr/bin/yelp' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1227299120 (LWP 14985)] [New Thread -1278719088 (LWP 14991)] [New Thread -1270252656 (LWP 14990)] [New Thread -1246962800 (LWP 14989)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 88002
Thread 1 (Thread -1227299120 (LWP 14985))
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 377079 ***