Re: [SyncEvolution] syncevolution --daemon=yes/no (was: RE: Alarms in the calendar: Evolution vs. vcal)
On Thu, 2010-04-08 at 14:18 +0100, Tino Keitel wrote:
On Thu, Apr 08, 2010 at 11:43:15 +0200, Patrick Ohly wrote:
[...]
> I suspect that you can avoid the problem using one of these methods:
> - configure with --with-xmltok=builtin
> - remove libxmltok1-dev and install libexpat1-dev instead
>
> In the meantime I'll try myself whether I can reproduce the problem when
> using libxmltok1-dev.
I rebuilt libsynthesis with --with-xmltok=builtin and replaced
libxmltok1-dev with libexpat1-dev in the build dependencies. Now the
segfault does not happen anymore.
I've not been able to reproduce the problem when using libxmltok. I did
find an uninitialized memory read reported by valgrind, but not one
which explains the segfault. Fix is in "master" of libsynthesis.
Another one points towards a problem in our own code
(http://bugzilla.moblin.org/show_bug.cgi?id=10468), plus there are some
know reports about issues in libical.
I'd like to get to the bottom of this. Would you mind doing one more
experiment with a syncevo-dbus-server using libxmltok? Please, run such
a syncevo-dbus-server under "valgrind --track-origins=yes" and report
back what you get.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.