evolution-data-server-2.22 crashed with SIGSEGV in poll()

[josete]

**If this is reproducible -- please run under Valgrind, and attach the Valgrind output here. This will help on isolating the fault and fixing it.**

Please see https://wiki.ubuntu.com/Valgrind for details on how to run Valgrind.

Binary package hint: evolution-data-server

Updating ubuntu from alpha-6 to the latest respository info on March/9 at 14:02 GMT+1

ProblemType: Crash
Architecture: amd64
Date: Sun Mar 9 14:00:01 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/evolution/evolution-data-server-2.22
NonfreeKernelModules: nvidia
Package: evolution-data-server 2.21.92-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: /usr/lib/evolution/evolution-data-server-2.22 --oaf-activate-iid=OAFIID:GNOME_Evolution_DataServer_CalFactory:1.2 --oaf-ior-fd=22
ProcEnviron:
 LANG=es_ES.UTF-8
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 SHELL=/bin/bash
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
 poll () from /lib/libc.so.6
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_loop_run () from /usr/lib/libglib-2.0.so.0
 bonobo_main () from /usr/lib/libbonobo-2.so.0
 ?? ()
Title: evolution-data-server-2.22 crashed with SIGSEGV in poll()
Uname: Linux 2.6.24-11-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video
SegvAnalysis:
 Segfault happened at: 0x7fe7a744627a: mov 0x8(%rbp),%r15
 PC (0x7fe7a744627a) ok
 source "0x8(%rbp)" (0x7fe7a7d9ccf8) in non-readable VMA region: 0x7fe7a7d96000-0x7fe7a7f95000 ---p /usr/lib/libplc4.so.0d
 destination "%r15" ok
SegvReason: reading VMA /usr/lib/libplc4.so.0d

[Apport retracing service (apport)]

StacktraceTop:poll () from /lib/libc.so.6
g_main_context_iterate (context=0x61ea80, block=1, dispatch=1, self=<value optimized out>)
IA__g_main_loop_run (loop=0x645b80) at /build/buildd/glib2.0-2.15.6/glib/gmain.c:2906
bonobo_main () at bonobo-main.c:311
main (argc=3, argv=<value optimized out>) at server.c:418

[C de-Avillez (hggdh2)]

Confirming, but we should still look for valgrind runs.