GNOME Bugzilla – Bug 467194
crash in Image Viewer: viewing jpgs
Last modified: 2007-09-10 03:19:32 UTC
Version: 2.16.2 What were you doing when the application crashed? viewing jpgs Distribution: Slackware Slackware 11.0.0 Gnome Release: 2.16.3 2007-03-03 (Dropline GNOME) BugBuddy Version: 2.16.0 Memory status: size: 98607104 vsize: 0 resident: 98607104 share: 0 rss: 48967680 rss_rlim: 0 CPU usage: start_time: 1187240087 rtime: 0 utime: 2015 stime: 0 cutime:1740 cstime: 0 timeout: 275 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/eog' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225991968 (LWP 11590)] [New Thread -1253024848 (LWP 11633)] [New Thread -1261413456 (LWP 11632)] 0xb76eed57 in ___newselect_nocancel () from /lib/tls/libc.so.6
+ Trace 155569
Thread 3 (Thread -1261413456 (LWP 11632))
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 and reopen this bug or report a new one. Thanks in advance!
I compiled eog with the -g option. Is this stack trace an improvement? Perhaps you would need me to compile the various libraries with debugging symbols. I see that this is not the latest version of eog. Distribution: Slackware Slackware 11.0.0 Gnome Release: 2.16.3 2007-03-03 (Dropline GNOME) BugBuddy Version: 2.16.0 Memory status: size: 92479488 vsize: 0 resident: 92479488 share: 0 rss: 42389504 rss_rlim: 0 CPU usage: start_time: 1189221462 rtime: 0 utime: 11327 stime: 0 cutime:11107 cstime: 0 timeout: 220 it_real_value: 0 frequency: 3 Backtrace was generated from '/usr/local/bin/eog' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1225943360 (LWP 13203)] [New Thread -1244243024 (LWP 13231)] [New Thread -1252971600 (LWP 13228)] 0xb7354071 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 161240
Thread 3 (Thread -1252971600 (LWP 13228))
Hm, not really. The stacktrace misses too many symbols to be useful. What were you doing when eog crashed?
I compiled glibc, glib, libjpeg and eog with the -g option. Still missing some symbols though. The crash seems to happen when I hit F11 to switch back and forth from full screen to a window. Memory status: size: 129253376 vsize: 0 resident: 129253376 share: 0 rss: 68849664 rss_rlim: 0 CPU usage: start_time: 1189288769 rtime: 0 utime: 745 stime: 0 cutime:686 cstime: 0 timeout: 59 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/local/bin/eog' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1226414400 (LWP 25941)] [New Thread -1254622288 (LWP 25963)] [New Thread -1263010896 (LWP 25962)] 0xb72e1071 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 161418
Thread 1 (Thread -1226414400 (LWP 25941))
This is as much symbol table information as I can get right now. Trying to recompile slackware gtk+2 package but the build breaks. Memory status: size: 85504000 vsize: 0 resident: 85504000 share: 0 rss: 49528832 rss_rlim: 0 CPU usage: start_time: 1189319229 rtime: 0 utime: 1839 stime: 0 cutime:1684 cstime: 0 timeout: 155 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/local/bin/eog' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1226565952 (LWP 12185)] [New Thread -1278051408 (LWP 12187)] [New Thread -1237656656 (LWP 12186)] 0xb72bc071 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 161468
Thread 1 (Thread -1226565952 (LWP 12185))
Well, that's a known bug, and it has been already solved in version 2.19. Thank you very much for your time! Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 320206 ***