After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 390262 - crash in Image Viewer: Hallo! Zur Vollansicht ...
crash in Image Viewer: Hallo! Zur Vollansicht ...
Status: RESOLVED INCOMPLETE
Product: eog
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-28 07:25 UTC by smojh
Modified: 2007-02-04 15:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description smojh 2006-12-28 07:25:29 UTC
Version: 2.16.1

What were you doing when the application crashed?
Hallo!

Zur Vollansicht geschaltet und F11 gedrueckt. 
Bilder wurden vom USB-Stick gelesen.

Viel Glueck beim Debuggen ;-))

Ciao
  Otto


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 109420544 vsize: 0 resident: 109420544 share: 0 rss: 41684992 rss_rlim: 0
CPU usage: start_time: 1167290326 rtime: 0 utime: 998 stime: 0 cutime:820 cstime: 0 timeout: 178 it_real_value: 0 frequency: 1

Backtrace was generated from '/usr/bin/eog'

(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 -1226697040 (LWP 5252)]
[New Thread -1290564704 (LWP 5254)]
[New Thread -1228465248 (LWP 5253)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226697040 (LWP 5252))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 free
    from /lib/tls/i686/cmov/libc.so.6
  • #5 cmsCloseProfile
    from /usr/lib/liblcms.so.1
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 eog_image_free_mem_private
  • #0 __kernel_vsyscall

Comment 1 Pedro de Medeiros 2006-12-29 17:56:03 UTC
This bug looks a lot like bug 387566.

Anyway, 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!
Comment 2 smojh 2006-12-31 13:03:42 UTC
Hi!

Here is the bug-trace. Hope it helps you to find the bug.
Ciao
   Otto

otto@kraxi:~$ gbd /usr/bin/eog 
bash: gbd: command not found
otto@kraxi:~$ run
bash: run: command not found
otto@kraxi:~$ gdb /usr/bin/eog 
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".

(gdb) run
Starting program: /usr/bin/eog 
[Thread debugging using libthread_db enabled]
[New Thread -1226438992 (LWP 6313)]
[New Thread -1270322272 (LWP 6318)]
[New Thread -1278714976 (LWP 6319)]
[Thread -1278714976 (LWP 6319) exited]
[Thread -1270322272 (LWP 6318) exited]
[New Thread -1270322272 (LWP 6320)]
[Thread -1270322272 (LWP 6320) exited]
[New Thread -1270322272 (LWP 6323)]
[New Thread -1278714976 (LWP 6324)]
[New Thread -1287599200 (LWP 6325)]
[New Thread -1295991904 (LWP 6326)]
[New Thread -1304384608 (LWP 6327)]
[Thread -1270322272 (LWP 6323) exited]
[Thread -1278714976 (LWP 6324) exited]
[Thread -1287599200 (LWP 6325) exited]
[Thread -1295991904 (LWP 6326) exited]
[Thread -1304384608 (LWP 6327) exited]
[New Thread -1295991904 (LWP 6328)]
[New Thread -1287599200 (LWP 6329)]
[New Thread -1304384608 (LWP 6330)]
[New Thread -1278714976 (LWP 6331)]
[New Thread -1270322272 (LWP 6332)]
[Thread -1278714976 (LWP 6331) exited]
[Thread -1295991904 (LWP 6328) exited]
[Thread -1287599200 (LWP 6329) exited]
[Thread -1270322272 (LWP 6332) exited]
[Thread -1304384608 (LWP 6330) exited]
[New Thread -1270322272 (LWP 6333)]
[New Thread -1304384608 (LWP 6334)]
[Thread -1270322272 (LWP 6333) exited]
[New Thread -1270322272 (LWP 6337)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1226438992 (LWP 6313)]
0x3537315f in ?? ()
(gdb) Quit
(gdb) quit
The program is running.  Exit anyway? (y or n) y
otto@kraxi:~$ 

Comment 3 Claudio Saavedra 2006-12-31 19:26:11 UTC
Seems like you forgot to actually make the trace. You need to run 'thread apply all bt' in gdb after the program crashes and before quiting. Please try again :-)
Comment 4 smojh 2007-01-01 17:05:59 UTC
Hello!

Hope that the trace is now correct.
Ciao
  Otto

otto@kraxi:~$ gdb /usr/bin/eog
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".

(gdb) run
Starting program: /usr/bin/eog 
[Thread debugging using libthread_db enabled]
[New Thread -1225976144 (LWP 5158)]

** (eog:5158): WARNING **: Error in parse: Fehler in Zeile 3382, Zeichen 5: Dokument endete unerwartet mit noch offenen Elementen - »RecentItem« war das letzte offene Element

** (eog:5158): WARNING **: Unable to complete parsing of the .recently-used file: Fehler in Zeile 3382, Zeichen 5: Dokument endete unerwartet mit noch offenen Elementen - »RecentItem« war das letzte offene Element


** (eog:5158): WARNING **: Error in parse: Fehler in Zeile 3382, Zeichen 5: Dokument endete unerwartet mit noch offenen Elementen - »RecentItem« war das letzte offene Element

** (eog:5158): WARNING **: Unable to complete parsing of the .recently-used file: Fehler in Zeile 3382, Zeichen 5: Dokument endete unerwartet mit noch offenen Elementen - »RecentItem« war das letzte offene Element

[New Thread -1269195872 (LWP 5183)]
[New Thread -1277588576 (LWP 5184)]
[Thread -1277588576 (LWP 5184) exited]
[Thread -1269195872 (LWP 5183) exited]
[New Thread -1269195872 (LWP 5189)]
[New Thread -1277588576 (LWP 5190)]
[New Thread -1286472800 (LWP 5191)]
[New Thread -1294865504 (LWP 5192)]
[Thread -1286472800 (LWP 5191) exited]
[Thread -1269195872 (LWP 5189) exited]
[Thread -1277588576 (LWP 5190) exited]
[Thread -1294865504 (LWP 5192) exited]
[New Thread -1294865504 (LWP 5193)]
[New Thread -1277588576 (LWP 5194)]
[New Thread -1269195872 (LWP 5195)]
[New Thread -1286472800 (LWP 5196)]
[New Thread -1303258208 (LWP 5197)]
[Thread -1294865504 (LWP 5193) exited]
[Thread -1277588576 (LWP 5194) exited]
[Thread -1269195872 (LWP 5195) exited]
[Thread -1286472800 (LWP 5196) exited]
[Thread -1303258208 (LWP 5197) exited]
[New Thread -1286472800 (LWP 5200)]
[New Thread -1303258208 (LWP 5201)]
[Thread -1286472800 (LWP 5200) exited]
[New Thread -1286472800 (LWP 5202)]

** (eog:5158): WARNING **: Error in parse: Fehler in Zeile 3382, Zeichen 5: Dokument endete unerwartet mit noch offenen Elementen - »RecentItem« war das letzte offene Element

** (eog:5158): WARNING **: Unable to complete parsing of the .recently-used file: Fehler in Zeile 3382, Zeichen 5: Dokument endete unerwartet mit noch offenen Elementen - »RecentItem« war das letzte offene Element

Program received signal SIGINT, Interrupt.
[Switching to Thread -1225976144 (LWP 5158)]
0xffffe410 in __kernel_vsyscall ()
(gdb) Quit
(gdb) thread apply all bt

The program is running.  Exit anyway? (y or n) y
otto@kraxi:~$ 
Comment 5 Pedro de Medeiros 2007-01-02 12:29:53 UTC
Actually, trace is incomplete. Please press return at the end of the screen instead of "q" to get the complete stack trace. :)
Comment 6 Claudio Saavedra 2007-02-04 15:40:01 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!