Public bug reported:

I have the very latest stuff from Ubuntu hardy-proposed, including the
latest libldap fixes:

ii  evolution                            2.22.2-0ubuntu1
ii  evolution-common                     2.22.2-0ubuntu1
ii  evolution-data-server                2.22.2-0ubuntu1
ii  evolution-data-server-common         2.22.2-0ubuntu1
ii  evolution-data-server-dbg            2.22.2-0ubuntu1
ii  evolution-dbg                        2.22.2-0ubuntu1
ii  evolution-dev                        2.22.2-0ubuntu1
ii  evolution-exchange                   2.22.2-0ubuntu1
ii  evolution-exchange-dbg               2.22.2-0ubuntu1
ii  evolution-plugins                    2.22.2-0ubuntu1
ii  evolution-webcal                     2.21.92-0ubuntu1
ii  libldap-2.4-2                        2.4.7-6ubuntu4.2i~ppa2
ii  libldap-2.4-2-dbg                    2.4.7-6ubuntu4.2i~ppa2 
ii  libldap2-dev                         2.4.7-6ubuntu4.2i~ppa2

I'm getting relatively frequent (a few a day) core dumps from evo-
exchange backend.  Here's a sample:

Core was generated by `/usr/lib/evolution/2.22/evolution-exchange-storage'.
Program terminated with signal 11, Segmentation fault.
[New process 20875]
[New process 20873]
#0  0xb7f69410 in __kernel_vsyscall ()
(gdb) bt 
#0  0xb7f69410 in __kernel_vsyscall ()
#1  0xb6e1ec07 in poll () from /lib/tls/i686/cmov/libc.so.6
#2  0xb6ef3e7f in ?? () from /usr/lib/libglib-2.0.so.0
#3  0xb6ef41e7 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#4  0xb70ce2e0 in ?? () from /usr/lib/libORBit-2.so.0
#5  0xb6f18a6f in ?? () from /usr/lib/libglib-2.0.so.0
#6  0xb6ea64fb in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb6e28e5e in clone () from /lib/tls/i686/cmov/libc.so.6
(gdb) thr apply all bt

Thread 2 (process 20873):
#0  get_message (stub=0x80a8910, folder_name=0x8128f30 "personal/Inbox", 
uid=0x8118300 "000001431fc2") at mail-stub-exchange.c:2447
#1  0x08064783 in connection_handler (source=0x80f5270, condition=G_IO_IN, 
data=0x80a8910) at mail-stub.c:271
#2  0xb6f24c5d in ?? () from /usr/lib/libglib-2.0.so.0
#3  0xb6ef0bf8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#4  0xb6ef3e5e in ?? () from /usr/lib/libglib-2.0.so.0
#5  0xb6ef41e7 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#6  0xb7119a93 in bonobo_main () from /usr/lib/libbonobo-2.so.0
#7  0x0805b8f3 in main (argc=3, argv=Cannot access memory at address 0x4
) at main.c:238

Thread 1 (process 20875):
#0  0xb7f69410 in __kernel_vsyscall ()
#1  0xb6e1ec07 in poll () from /lib/tls/i686/cmov/libc.so.6
#2  0xb6ef3e7f in ?? () from /usr/lib/libglib-2.0.so.0
#3  0xb6ef41e7 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#4  0xb70ce2e0 in ?? () from /usr/lib/libORBit-2.so.0
#5  0xb6f18a6f in ?? () from /usr/lib/libglib-2.0.so.0
#6  0xb6ea64fb in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb6e28e5e in clone () from /lib/tls/i686/cmov/libc.so.6


Looking at the source code it appears to be dying here:

        } else {
                SoupBuffer *response;

                status = e2k_context_get (mse->ctx, NULL, mmsg->href,
                                          &content_type, &response);
==>     len = response->length;
                body = g_strndup (response->data, response->length);
                soup_buffer_free (response);
        }

Apparently e2k_context_get() failed which means response was not set,
but this is not checked for by the code:

(gdb) thr 2     
[Switching to thread 2 (process 20873)]#0  get_message (stub=0x80a8910, 
folder_name=0x8128f30 "personal/Inbox", uid=0x8118300 "000001431fc2") at 
mail-stub-exchange.c:2447
2447    mail-stub-exchange.c: No such file or directory.
        in mail-stub-exchange.c
(gdb) p response
$1 = (SoupBuffer *) 0x1
(gdb) p status
$2 = 403

I'm not sure what a status of 403 from e2k_context_get() means, but it's
unlikely to mean "success" :-).

** Affects: evolution-exchange (Ubuntu)
     Importance: Undecided
         Status: New

-- 
evo-exchange dumps core retrieving email
https://bugs.launchpad.net/bugs/236781
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to