Created attachment 482177 [details]
File: backtrace

Thanks for a bug report. Seeing the place of the crash this seems to me like some memory corruption, which is probably not that simple to reproduce? If you can reproduce it, then I would suggest to run evolution under valgrind, like this:
   $ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>log.txt
which may show us whether there was any memory corruption or not. Thanks in advance.

Thread 1 (Thread 0xae8f8b70 (LWP 2031)):
#0  malloc_consolidate (av=0xb2100010) at malloc.c:5155
#1  0x00e40f07 in _int_free (av=0xb2100010, p=<value optimized out>, have_lock=0) at malloc.c:5034
#2  0x00b34137 in g_free (mem=0xb2101d78) at gmem.c:263
#3  0x00b1a0b0 in g_mkdir_with_parents (pathname=0xb2101ab0 "...", mode=448) at gfileutils.c:124
#4  0x07e97a15 in camel_uid_cache_new (filename=0xb2101cf0 "...") at camel-uid-cache.c:65
#5  0x020c1b33 in fetch_mail_exec (m=0x9e8ed58) at mail-ops.c:295
#6  0x020bc549 in mail_msg_proxy (msg=0x9e8ed58) at mail-mt.c:469
#7  0x00b593a1 in g_thread_pool_thread_proxy (data=0x9f1b500) at gthreadpool.c:319
#8  0x00b56bd0 in g_thread_create_proxy (data=0x9f0a5a0) at gthread.c:1897
#9  0x00614e99 in start_thread (arg=0xae8f8b70) at pthread_create.c:301
#10 0x00ea9d2e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133

Hi, Milan --

I did what you suggested above and it came up with only one line:

bash: valgrind: command not found...

I hope this helps.

Larry Cafiero

Created attachment 915195 [details]
Comment

(This comment was longer than 65,535 characters and has been moved to an attachment by Red Hat Bugzilla).

Thanks for the update. I see from the log that everything is about the pop3 account you have, it has some invalid writes, which then can cause basically anything.

Could you install debuginfo packages for evolution-data-server and evolution and then rerun the valgrind and attach (do not paste it as a comment) the stripped valgrind log, please? It'll contain more detailed information about place in the source code where the issues is caused.

Also, do you know what the actual error with the server is, please? You might get everything what's going on in POP3 with this command:
   $ CAMEL_DEBUG=all evolution 2>&1 | grep POP3 >log2.txt

Created attachment 482771 [details]
Results of debug asked to perform

Milan -- Here is the text file resulting from

  $ CAMEL_DEBUG=all evolution 2>&1 | grep POP3 >log2.txt

(I named it log_pop.txt instead of log2.txt)

As it stands now, after running debuginfo-install as you suggested, Evolution tends to be working OK going forward.

(In reply to comment #6)
> As it stands now, after running debuginfo-install as you suggested, Evolution
> tends to be working OK going forward.

Thanks for the update. I see the log is cut at the end, but from the above I understood that there was no issue since installing debuginfo packages. I suppose it's just a coincidence, the POP3 log shows no issue with the server, where I believe some error returned from the server is required to reproduce this.

Could you run evolution from a console for some time, and when/if it'll crash then get last page or two of messages from the console, please? Instead of the above command, use this to run evolution, please:
   $ CAMEL_DEBUG=all evolution | grep POP3
It may show us everything what comes on pop3 and also error messages. And because not pushing to file, then the console may take care of not cutting the output. Thanks in advance.

Backtrace analysis found this bug to be similar to bug #781872, closing as duplicate.

Bugs which were found to be similar to this bug: bug #757771, bug #781872

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 781872 ***