evo-exchange dumps core retrieving email
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
evolution-exchange |
Fix Released
|
Critical
|
|||
evolution-exchange (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Hardy |
Fix Released
|
Medium
|
Unassigned |
Bug Description
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-
ii evolution-
ii evolution-
ii evolution-dbg 2.22.2-0ubuntu1
ii evolution-dev 2.22.2-0ubuntu1
ii evolution-exchange 2.22.2-0ubuntu1
ii evolution-
ii evolution-plugins 2.22.2-0ubuntu1
ii evolution-webcal 2.21.92-0ubuntu1
ii libldap-2.4-2 2.4.7-6ubuntu4.
ii libldap-2.4-2-dbg 2.4.7-6ubuntu4.
ii libldap2-dev 2.4.7-6ubuntu4.
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/
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/
#2 0xb6ef3e7f in ?? () from /usr/lib/
#3 0xb6ef41e7 in g_main_loop_run () from /usr/lib/
#4 0xb70ce2e0 in ?? () from /usr/lib/
#5 0xb6f18a6f in ?? () from /usr/lib/
#6 0xb6ea64fb in start_thread () from /lib/tls/
#7 0xb6e28e5e in clone () from /lib/tls/
(gdb) thr apply all bt
Thread 2 (process 20873):
#0 get_message (stub=0x80a8910, folder_
#1 0x08064783 in connection_handler (source=0x80f5270, condition=G_IO_IN, data=0x80a8910) at mail-stub.c:271
#2 0xb6f24c5d in ?? () from /usr/lib/
#3 0xb6ef0bf8 in g_main_
#4 0xb6ef3e5e in ?? () from /usr/lib/
#5 0xb6ef41e7 in g_main_loop_run () from /usr/lib/
#6 0xb7119a93 in bonobo_main () from /usr/lib/
#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/
#2 0xb6ef3e7f in ?? () from /usr/lib/
#3 0xb6ef41e7 in g_main_loop_run () from /usr/lib/
#4 0xb70ce2e0 in ?? () from /usr/lib/
#5 0xb6f18a6f in ?? () from /usr/lib/
#6 0xb6ea64fb in start_thread () from /lib/tls/
#7 0xb6e28e5e in clone () from /lib/tls/
Looking at the source code it appears to be dying here:
} else {
SoupBuffer *response;
status = e2k_context_get (mse->ctx, NULL, mmsg->href,
==> 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_
2447 mail-stub-
in mail-stub-
(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" :-).
Related branches
Changed in evolution-exchange: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in evolution-exchange: | |
status: | Unknown → New |
Changed in evolution-exchange: | |
status: | New → Fix Released |
Changed in evolution-exchange: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in evolution-exchange: | |
importance: | Unknown → Critical |
I can't figure out how to reference an upstream bug, but I believe this bug has already been reported upstream to the GNOME bugzilla, here:
http:// bugzilla. gnome.org/ show_bug. cgi?id= 532844