GNOME Bugzilla – Bug 404355
crash in Evolution: Looking at high-res pict...
Last modified: 2007-04-16 20:18:09 UTC
What were you doing when the application crashed? Looking at high-res pictures from within an e-mail. It crashed when I opened the third one. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 341225472 vsize: 341225472 resident: 91127808 share: 18612224 rss: 91127808 rss_rlim: -1 CPU usage: start_time: 1170614255 rtime: 1086 utime: 974 stime: 112 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution-2.8' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47528756391280 (LWP 5984)] [New Thread 1115969872 (LWP 6156)] [New Thread 1107577168 (LWP 6155)] [New Thread 1107310928 (LWP 6137)] [New Thread 1098918224 (LWP 6120)] [New Thread 1090525520 (LWP 6119)] [New Thread 1082132816 (LWP 6116)] (no debugging symbols found) 0x00002b3a225815cf in waitpid () from /lib/libc.so.6
+ Trace 107975
Thread 7 (Thread 1082132816 (LWP 6116))
Thread 6 (Thread 1090525520 (LWP 6119))
Thread 5 (Thread 1098918224 (LWP 6120))
Thread 4 (Thread 1107310928 (LWP 6137))
Thread 2 (Thread 1115969872 (LWP 6156))
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!
Created attachment 81947 [details] Plain text file (hopefully) containing debugging information you'll need Hopefully I did this correctly. Followed the ubuntu-specific instructions from http://live.gnome.org/GettingTraces/DistroSpecificInstructions <-there and copied/pasted from bug-buddy. Hope that helps!
Unfortunately the trace hasn't improved much. It's suffering from an existing problem that sometimes happens with Bug Buddy interfering with the stack trace. Not your fault, but we'd still like to get a better trace. Can you try running evolution under gdb (see http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running for how to do this) and we should be able to get a better trace. Thanks for your feedback here!
Created attachment 81953 [details] Debug symbols attempt numero dos How's this?
Much better! Looks similar to Bug 392391 and Bug 358437, but I think this is still sufficiently different that it's possibly a different bug. Marking as NEW, and now hopefully the Evolution developers will be able to find out exactly what went wrong here with the information you've provided. Thanks!
Copying fixed stacktrace into the comments to make searching for duplicates easier.
+ Trace 108274
Great, thanks! In the meantime, I'll just download photos from e-mails.
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 273386 ***