GNOME Bugzilla – Bug 639708
Crash on startup reading email
Last modified: 2011-01-18 04:04:56 UTC
Code crashes when starting up when reading from pop server gdb output: GNU gdb (GDB) Fedora (7.2-26.fc14) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/evolution...Reading symbols from /usr/lib/debug/usr/bin/evolution.debug...done. done. (gdb) run Starting program: /usr/bin/evolution [Thread debugging using libthread_db enabled] [New Thread 0xb7db7b70 (LWP 9492)] (evolution:9489): evolution-network-manager-WARNING **: network_manager_check_initial_state: Timeout was reached [New Thread 0xb2469b70 (LWP 9504)] [New Thread 0xb1affb70 (LWP 9505)] [New Thread 0xb12feb70 (LWP 9506)] [New Thread 0xb0afdb70 (LWP 9507)] [New Thread 0xb02fcb70 (LWP 9508)] [New Thread 0xafafbb70 (LWP 9509)] [New Thread 0xaf2fab70 (LWP 9510)] [New Thread 0xaeaf9b70 (LWP 9511)] [New Thread 0xae2f8b70 (LWP 9512)] [Thread 0xaf2fab70 (LWP 9510) exited] [Thread 0xb02fcb70 (LWP 9508) exited] [New Thread 0xb02fcb70 (LWP 9513)] [Thread 0xb02fcb70 (LWP 9513) exited] [New Thread 0xb02fcb70 (LWP 9514)] [New Thread 0xaf2fab70 (LWP 9515)] [New Thread 0xadaf7b70 (LWP 9516)] [New Thread 0xad2f6b70 (LWP 9517)] [New Thread 0xacaf5b70 (LWP 9518)] [New Thread 0xac2f4b70 (LWP 9519)] [New Thread 0xabaf3b70 (LWP 9520)] [New Thread 0xab2f2b70 (LWP 9521)] [Thread 0xab2f2b70 (LWP 9521) exited] [Thread 0xad2f6b70 (LWP 9517) exited] [Thread 0xacaf5b70 (LWP 9518) exited] [New Thread 0xacaf5b70 (LWP 9522)] [New Thread 0xad2f6b70 (LWP 9523)] [New Thread 0xab2f2b70 (LWP 9524)] [Thread 0xab2f2b70 (LWP 9524) exited] [Thread 0xacaf5b70 (LWP 9522) exited] [Thread 0xad2f6b70 (LWP 9523) exited] [New Thread 0xad2f6b70 (LWP 9548)] [New Thread 0xacaf5b70 (LWP 9549)] [New Thread 0xab2f2b70 (LWP 9550)] [New Thread 0xa69f5b70 (LWP 9551)] [Thread 0xa69f5b70 (LWP 9551) exited] [New Thread 0xa69f5b70 (LWP 9552)] [New Thread 0xa61edb70 (LWP 9553)] [Thread 0xa61edb70 (LWP 9553) exited] [New Thread 0xa61edb70 (LWP 9554)] [New Thread 0xa59ecb70 (LWP 9555)] [Thread 0xa59ecb70 (LWP 9555) exited] [Thread 0xab2f2b70 (LWP 9550) exited] [Thread 0xafafbb70 (LWP 9509) exited] [Thread 0xa69f5b70 (LWP 9552) exited] (evolution:9489): camel-pop3-provider-CRITICAL **: pop3_get_message_time_from_cache: assertion `uid != NULL' failed Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xadaf7b70 (LWP 9516)] g_str_hash (v=0x0) at gstring.c:134 134 guint32 h = *p; (gdb) (gdb) thread apply all bt
+ Trace 225558
Thread 15 (Thread 0xadaf7b70 (LWP 9516))
(gdb)
GNU gdb (GDB) Fedora (7.2-26.fc14) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/evolution...Reading symbols from /usr/lib/debug/usr/bin/evolution.debug...done. done. (gdb) run Starting program: /usr/bin/evolution [Thread debugging using libthread_db enabled] [New Thread 0xb7db7b70 (LWP 10082)] [New Thread 0xb2469b70 (LWP 10094)] [New Thread 0xb1affb70 (LWP 10095)] [New Thread 0xb12feb70 (LWP 10096)] [New Thread 0xb0afdb70 (LWP 10097)] [New Thread 0xb02fcb70 (LWP 10098)] [New Thread 0xafafbb70 (LWP 10099)] [New Thread 0xaf2fab70 (LWP 10100)] [New Thread 0xaeaf9b70 (LWP 10101)] [New Thread 0xae2f8b70 (LWP 10102)] [Thread 0xaf2fab70 (LWP 10100) exited] [Thread 0xb02fcb70 (LWP 10098) exited] [New Thread 0xb02fcb70 (LWP 10103)] [New Thread 0xaf2fab70 (LWP 10104)] [New Thread 0xadaf7b70 (LWP 10105)] [New Thread 0xad2f6b70 (LWP 10106)] [New Thread 0xacaf5b70 (LWP 10107)] [New Thread 0xac2f4b70 (LWP 10108)] [New Thread 0xabaf3b70 (LWP 10110)] [New Thread 0xab2f2b70 (LWP 10112)] [Thread 0xacaf5b70 (LWP 10107) exited] [Thread 0xad2f6b70 (LWP 10106) exited] [Thread 0xab2f2b70 (LWP 10112) exited] [New Thread 0xab2f2b70 (LWP 10113)] [New Thread 0xad2f6b70 (LWP 10114)] [New Thread 0xacaf5b70 (LWP 10115)] [Thread 0xacaf5b70 (LWP 10115) exited] [Thread 0xad2f6b70 (LWP 10114) exited] [Thread 0xab2f2b70 (LWP 10113) exited] [New Thread 0xab2f2b70 (LWP 10116)] [New Thread 0xad2f6b70 (LWP 10117)] [New Thread 0xacaf5b70 (LWP 10118)] [New Thread 0xa69f5b70 (LWP 10119)] [Thread 0xa69f5b70 (LWP 10119) exited] [New Thread 0xa69f5b70 (LWP 10131)] [New Thread 0xa61edb70 (LWP 10132)] [Thread 0xa61edb70 (LWP 10132) exited] [New Thread 0xa61edb70 (LWP 10133)] [New Thread 0xa57ffb70 (LWP 10134)] [Thread 0xa57ffb70 (LWP 10134) exited] [Thread 0xab2f2b70 (LWP 10116) exited] [Thread 0xafafbb70 (LWP 10099) exited] (evolution:10079): camel-pop3-provider-CRITICAL **: pop3_get_message_time_from_cache: assertion `uid != NULL' failed Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xadaf7b70 (LWP 10105)] g_str_hash (v=0x0) at gstring.c:134 134 guint32 h = *p; (gdb) q A debugging session is active. Inferior 1 [process 10079] will be killed.
100% reproducable
If possible, can you please attach valgrind log in bug 639201 Please have a look at https://wiki.ubuntu.com/Valgrind for more information. *** This bug has been marked as a duplicate of bug 639201 ***
Since this is a duplicate do you still need the valgrind? I removed most of the outstanding email from the server and this started working again, I believe the transfer was timing out, so the problem will occur again when the number of emails on the server builds.
If you can get us valgrind, it will be helpful and you can paste valgrind log in original bug 639201. Evolution will be very slow when you run it under valgring.
Well as soon as it starts crashing again I will do a valgrind to get the information but it might take a couple of days before it crashes again.