Ubuntu
evolution-data-server package

  1. Bug #135471
  2. Comment #11

Comment 11 for bug 135471

Revision history for this message
C de-Avillez (hggdh2) wrote :

indeed, easy to trigger, it seems. I loaded contacts, and ran gdb against evolution-data-server. On the Ev window I then run a search against "any field contains". Immediate SIGABRT.

Here's the BT:

Program received signal SIGABRT, Aborted.
[Switching to Thread 1082399056 (LWP 15240)]
0x00002ae1690ce765 in raise () from /lib/libc.so.6
(gdb) bt
#0 0x00002ae1690ce765 in raise () from /lib/libc.so.6
#1 0x00002ae1690d01c0 in abort () from /lib/libc.so.6
#2 0x00002ae16910760b in __libc_message () from /lib/libc.so.6
#3 0x00002ae16910eb0a in _int_free () from /lib/libc.so.6
#4 0x00002ae1691126fc in free () from /lib/libc.so.6
#5 0x00002ae16e6bac82 in ?? () from /usr/lib/evolution-data-server-1.2/extensions/libebookbackendfile.so
#6 0x00002ae1683bf904 in g_thread_create_proxy (data=0x6424a0)
    at /build/buildd/glib2.0-2.14.1/glib/gthread.c:635
#7 0x00002ae168e88317 in start_thread () from /lib/libpthread.so.0
#8 0x00002ae169170d5d in clone () from /lib/libc.so.6
#9 0x0000000000000000 in ?? ()

Looks like memory issues...