On Mo, 2010-04-12 at 17:57 +0100, Tino Keitel wrote: > On Thu, Apr 08, 2010 at 16:42:11 +0200, Patrick Ohly wrote: > > [...] > > > 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. > > Hi, > > I attached is a valgrind output of syncevo-dbus-server with > libsynthesis git master as of today.
Unfortunately that doesn't help much. Tino, I've stressed your patience enough. Despite what I said earlier, let's move on. David, in case you didn't read the relevant emails, Tino had a problem with a somewhat mysterious jump to an illegal address inside libxmlparse, the library from libxmltok1-dev. libexpat from libexpat1-dev is what we use in binaries on syncevolution.org. I believe it is the successor of libxmltok. Can you switch the Debian package dependencies of libsynthesis so that it uses libexpat1-dev instead of libxmltok1-dev? That should avoid the issue, whatever it was. -- 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. _______________________________________________ SyncEvolution mailing list SyncEvolution@syncevolution.org http://lists.syncevolution.org/listinfo/syncevolution
