GNOME Bugzilla – Bug 387566
crash in Image Viewer: Looking at photos (~2.1M...
Last modified: 2006-12-29 18:04:35 UTC
Version: 2.16.1 What were you doing when the application crashed? Looking at photos (~2.1MB) by double-clicking on them in nautilus Several after each other... Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 2002944 vsize: 0 resident: 2002944 share: 0 rss: 692224 rss_rlim: 0 CPU usage: start_time: 1166544091 rtime: 0 utime: 126 stime: 0 cutime:0 cstime: 0 timeout: 126 it_real_value: 0 frequency: 13294 Backtrace was generated from '/usr/bin/eog' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
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!
Bug-Buddy did not give me any more info after installing eog-dbgsym, so I tried the gdb method. I don't know if the following is correct, considering the fact that I start eog by double-clicking a .jpg in nautilus. COMMAND: ps aux | grep eog | grep -v grep RESULT: wietse 8354 0.2 1.2 18156 6336 ? S 22:17 0:00 /usr/lib/libgnomeui-0/gnome_segv eog 11 2.16.1 COMMAND: gdb $(which eog) 8354 RESULT: GNU gdb 6.4.90-debian Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i486-linux-gnu"...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". Attaching to program: /usr/bin/eog, process 8354 0xffffe410 in __kernel_vsyscall () (gdb) cont Continuing. Warning: Cannot insert breakpoint -3. Error accessing memory address 0xb2c0: Input/output error. (gdb) thread apply all bt (gdb) bt
+ Trace 95487
New crash while looking at pictures gave me this information: Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 179036160 vsize: 0 resident: 179036160 share: 0 rss: 139153408 rss_rlim: 0 CPU usage: start_time: 1166902702 rtime: 0 utime: 9053 stime: 0 cutime:8666 cstime: 0 timeout: 387 it_real_value: 0 frequency: 2 Backtrace was generated from '/usr/bin/eog' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1226102592 (LWP 7269)] [New Thread -1278751840 (LWP 7272)] [New Thread -1227953248 (LWP 7270)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 96537
Thread 1 (Thread -1226102592 (LWP 7269))
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 354106 ***