GNOME Bugzilla – Bug 359801
crash in Evolution: Clicking from IMAP folde...
Last modified: 2006-10-10 11:57:23 UTC
What were you doing when the application crashed? Clicking from IMAP folder to trash, then back to another folder quickly causes evolution to crash. I am able to reproduce this. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 28000256 vsize: 0 resident: 114462720 share: 0 rss: 114462720 rss_rlim: 0 CPU usage: start_time: 2641 rtime: 0 utime: 1160030852 stime: 0 cutime:377 cstime: 0 timeout: 362 it_real_value: 0 frequency: 15 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 805931280 (LWP 6569)] [New Thread 868480240 (LWP 6582)] [New Thread 860091632 (LWP 6579)] [New Thread 840967408 (LWP 6578)] [New Thread 832177392 (LWP 6573)] [New Thread 823788784 (LWP 6571)] 0x0e619220 in __waitpid_nocancel () from /lib/libc.so.6
+ Trace 74626
Thread 6 (Thread 823788784 (LWP 6571))
Thread 5 (Thread 832177392 (LWP 6573))
Thread 4 (Thread 840967408 (LWP 6578))
Thread 3 (Thread 860091632 (LWP 6579))
Thread 2 (Thread 868480240 (LWP 6582))
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Here is another stack trace: 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 "powerpc-linux-gnu"...(no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /usr/bin/evolution-2.8 (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 805575792 (LWP 17438)] CalDAV Eplugin starting up ... (evolution-2.8:17438): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one (evolution-2.8:17438): e-utils-WARNING **: Plugin 'Spamassassin junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0' ** (evolution-2.8:17438): DEBUG: mailto URL command: evolution %s ** (evolution-2.8:17438): DEBUG: mailto URL program: evolution [New Thread 823719152 (LWP 17448)] [New Thread 832107760 (LWP 17449)] [New Thread 840889584 (LWP 17450)] [Thread 832107760 (LWP 17449) exited] [New Thread 849278192 (LWP 17451)] [Thread 849278192 (LWP 17451) exited] [New Thread 849278192 (LWP 17456)] [New Thread 832107760 (LWP 17457)] [New Thread 868005104 (LWP 17460)] (evolution-2.8:17438): e-data-server-WARNING **: Error in parsing: Unexpected token encountered: 0 parse_term_free: unknown type: 274046064 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 849278192 (LWP 17456)] 0x0f5535e0 in memset () from /lib/libc.so.6 (gdb) (gdb) (gdb) thread apply all bt
+ Trace 74822
Thread 1 (Thread 805575792 (LWP 17438))
Thanks for the feedback, Matt. :) This one is better. However, that stacktrace still does not have any debugging symbols. Could you please install the relevant debug packages [1], and get us a stacktrace with debugging symbols? [1] debugging packages for evolution and evolution-data-server, plus debugging packages for some basic GNOME libs. More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions
*** Bug 359799 has been marked as a duplicate of this bug. ***
Ok I installed the debug symbols, however I could no longer get it to crash when running under gdb. I was able to crash it running normally and capture the stacktrace from bug buddy. Hopefully this one helps, I will keep trying to crash while running under gdb. Thank you. Memory status: size: 27545600 vsize: 0 resident: 115306496 share: 0 rss: 115306496 rss_rlim: 0 CPU usage: start_time: 5506 rtime: 0 utime: 1160108586 stime: 0 cutime:539 cstime: 0 timeout: 510 it_real_value: 0 frequency: 29 Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 805575792 (LWP 6487)] [New Thread 869266672 (LWP 6516)] [New Thread 840889584 (LWP 6506)] [New Thread 832107760 (LWP 6500)] [New Thread 823719152 (LWP 6498)] 0x0f574220 in __waitpid_nocancel () from /lib/libc.so.6
+ Trace 74837
Thread 3 (Thread 840889584 (LWP 6506))
Thanks, Matt. :)
Looks like bug 359785 to me. 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 359785 ***