GNOME Bugzilla – Bug 569329
[groupwise] EDS crashed when checking contacts in Novell GroupWise Address Book
Last modified: 2010-09-01 14:49:36 UTC
Steps to reproduce: EDS crashed when checking contacts in Novell GroupWise Address Book Stack trace: (evolution-data-server-2.26:28243): libegroupwise-CRITICAL **: e_gw_item_get_item_type: assertion `E_IS_GW_ITEM (item)' failed (evolution-data-server-2.26:28243): libegroupwise-CRITICAL **: e_gw_item_get_item_type: assertion `E_IS_GW_ITEM (item)' failed (evolution-data-server-2.26:28243): libegroupwise-CRITICAL **: e_gw_item_get_field_value: assertion `E_IS_GW_ITEM(item)' failed (evolution-data-server-2.26:28243): libegroupwise-CRITICAL **: e_gw_item_get_field_value: assertion `E_IS_GW_ITEM(item)' failed Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffd6ff5950 (LWP 28452)] e_gw_item_get_full_name (item=0x0) at e-gw-item.c:884 884 { (gdb) t a a bt
+ Trace 211927
Thread 37 (Thread 0x7fffd87f8950 (LWP 28455))
Thread 36 (Thread 0x7fffd67f4950 (LWP 28454))
Thread 35 (Thread 0x7fffd6ff5950 (LWP 28452))
Thread 34 (Thread 0x7fffd77f6950 (LWP 28451))
Thread 33 (Thread 0x7fffd7ff7950 (LWP 28450))
Thread 9 (Thread 0x7fffe37fe950 (LWP 28322))
(gdb) Other information: Found this crash in trunk build Evolution revision: 37139 EDS revision: 9971
I got this crash again in 2.27.3 build. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xadafcb90 (LWP 15732)] 0xb6632eba in e_gw_item_get_full_name (item=0x81dee68) at e-gw-item.c:891 (gdb) t a a bt
+ Trace 215914
Thread 31 (Thread 0xadafcb90 (LWP 15732))
*** Bug 597255 has been marked as a duplicate of this bug. ***
Created attachment 149325 [details] [review] proposed eds patch for evolution-data-server; I do not have groupwise, thus this is just a blind shot into the darkness... It seems that the fetching of contact-list details failed for some reason and was used previously freed EGWItem pointer in reading. This is trying to check for failure conditions. Such failed contact-lists will not have members, I guess, but I'm not sure, maybe only not all, hard to tell. Can anyone test this, please?
This patch fixes the issue for me. Thanks!!
After upgrading to e-d-s 2.28.2, this issue is back: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f2866fda910 (LWP 6869)] e_gw_item_get_full_name (item=0x0) at e-gw-item.c:909 909 { (gdb) thread apply all bt
+ Trace 219661
Thread 10 (Thread 0x7f28657d7910 (LWP 6870))
Thread 9 (Thread 0x7f2866fda910 (LWP 6869))
Thread 7 (Thread 0x7f2868b74910 (LWP 6861))
*** Bug 607435 has been marked as a duplicate of this bug. ***
There is a patch attached in bug 607435 as well. https://bugzilla.gnome.org/show_bug.cgi?id=607435#c7
(In reply to comment #5) > After upgrading to e-d-s 2.28.2, this issue is back Did you apply the patch too? Also, the above patch also prevents using of uninitialized memory, whereas the patch from the bug #607435 seems to check only for NULL/not-NULL values, but the uninitialized 'item' variable can be pretty anything, not only NULL. Maybe both can be used.
As spoken on IRC: Created commit 2130b68 in eds master (2.31.92+)