GNOME Bugzilla – Bug 334798
evolution-exchange-storage crashes constantly
Last modified: 2007-08-22 13:23:39 UTC
Steps to reproduce: 1. Create an exchange account 2. Use it 3. Evolution-exchange-storage will crash Stack trace: Debugging Information: Backtrace was generated from '/usr/libexec/evolution-exchange-storage' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (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) (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) (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) [Thread debugging using libthread_db enabled] [New Thread -1233307968 (LWP 4659)] [New Thread -1234728016 (LWP 4660)] (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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 66989
Thread 1 (Thread -1233307968 (LWP 4659))
Other information: When running Evolution with Exchange, the evolution-exchange-storage process constantly crashes. Sometimes right when Evolution is opened, sometimes after a long period of use. Please DO NOT file this as a duplicate of bug #318624, unless you re-open that bug. evolution 2.6.0-0ubuntu1 evolution-data-server 1.6.0-0ubuntu1 evolution-exchange 2.6.0-0ubuntu1 evolution-plugins 2.6.0-0ubuntu1 evolution-webcal 2.5.90-0ubuntu1
looks like some libsoup issue. Which is your libsoup version? Assigning to Chenthill and moving to libsoup.
I've tested with libsoup2.2.91-ubuntu, and 2.2.7-2 (Debian).
*** Bug 335590 has been marked as a duplicate of this bug. ***
Another similar bug http://bugzilla.gnome.org/show_bug.cgi?id=322901
*** Bug 331096 has been marked as a duplicate of this bug. ***
*** Bug 325758 has been marked as a duplicate of this bug. ***
Another Ubuntu backtrace: Backtrace was generated from '/usr/libexec/evolution-exchange-storage' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (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) [Thread debugging using libthread_db enabled] [New Thread -1233254720 (LWP 4950)] [New Thread -1234674768 (LWP 4951)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 67458
Thread 1 (Thread -1233254720 (LWP 4950))
Our exchange server was recently upgraded from Exchange 2000 to Exchange 2003, and I have been running for a week on the new server with no crashes. This bug seems to be connected to Exchange 2000 somehow.
does this bug still happen for anyone else?
Hallo I also suffer from this bug. I cannot use evolution for more than 5minutes. Here are results of my investigation: I have tested on gentoo evolution 2.4, 2.6 evolution-exchange 2.4.2, 2.6.0 libsoup 2.2.7, 2.2.92 glib 2.6.5, 2.8.6 1. This bug is probably related to specific Exchange 2000 instalations. Our exchange often resets TCP connections, do not ask me why, it just does. 2. It is not related to evolution-exchange, problem is somewhere between libsoup and glib. 3. stack trace produced by bug-buddy is different from gdb. 4. in gdb I see similar backtraces (gdb) thread 2 [Switching to thread 2 (Thread -1227699280 (LWP 10392))]#0 0x4771c375 in libgnomeui_module_info_get () from /usr/lib/libgnomeui-2.so.0 (gdb) bt
+ Trace 68638
5. SEGFAULT allways occurs in some function in soup-message-io.c like io_write Each of these functions contains code like this: static void io_write (SoupSocket *sock, SoupMessage *msg) { SoupMessagePrivate *priv = SOUP_MESSAGE_GET_PRIVATE (msg); SoupMessageIOData *io = priv->io_data; none of these functions checks value of priv. when SEGFAULT occurs priv is allways NULL and msg is ALLWAYS corrupted same way (gdb) p priv $74 = (SoupMessagePrivate *) 0x0 (gdb) p *msg $73 = {parent = {g_type_instance = {g_class = 0xb70348d0}, ref_count = 3070445776, qdata = 0xaaaaaaaa}, method = 0xaaaaaaaa <Address 0xaaaaaaaa out of bounds>, status_code = 2863311530, reason_phrase = 0xaaaaaaaa <Address 0xaaaaaaaa out of bounds>, request = {owner = 2863311530, body = 0xaaaaaaaa <Address 0xaaaaaaaa out of bounds>, length = 2863311530}, request_headers = 0xaaaaaaaa, response = { owner = 2863311530, body = 0xaaaaaaaa <Address 0xaaaaaaaa out of bounds>, length = 2863311530}, response_headers = 0xaaaaaaaa, status = 2863311530} As you see, whole msg structure is overwritten with weird value 0xaaaaaaaa. Everytime evolution-exchange crashes msg contains these values. I tried to find this constant in sources of glib, evoluton-*, libsoup and others, without any success. Ivan
As per a long-ago discussion with Parag and Harish, I'm moving the soup connector bugs to the Evolution Exchange product, because I have no way of reproducing these bugs myself, so if they stay filed against libsoup, they're never going to get fixed.
*** This bug has been marked as a duplicate of 320015 ***
Can anyone try with the svn trunk version of libsoup or GNOME 2.18 version of libsoup and report back the status?