On 02/29/2012 03:22 PM, Patrick Ohly wrote:
On Mon, 2012-02-27 at 14:32 +0200, Juha Pahkala wrote:
Sure. Just did and sent the output to you.
The concatenation in the XML message dump is indeed an artifact of how
buffers are handled; it's not the root cause of the problem.
I tried to reproduce the decoding problem by feeding the same message
into a local SyncEvolution installation, but after making a few changes
to the message to fit into a normal session the problem didn't occur.
Juha, I have to rely on you for some remote debugging.
Sure thing, no problem, other than the fact that I'll be away for two
weeks from Saturday onwards, but before and after, I'm glad to help.
As a first step, please use the pre-release 1.2.99+20120228+SE+cb0b7f6
+SYSYNC+5e0f652 from the experimental apt repo on syncevolution.org or
from dowloads.syncevolution.org.
I tried the .deb package, but it depended on kde, so I skipped it and
tried the binary build instead. That gave me some dbus version error,
can't recall what it was. Anyhow, compiling the source worked out, and I
ran it again. Output sent to you.
It has additional debug printing enabled in the SyncML Toolkit. Please
send me another server-side log of a failed sync attempt with that
version.
Perhaps it'll tell me something (not sure yet).
If it doesn't, do you know gdb well enough to step through the source
code manually?
Hmm, don't know gdb at all, but I do have some experience of debugging
and stepping through source code... so I'm pretty sure I'll be able to help.
br, juhis
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
