Re: [SyncEvolution] sync timeouts for syncevo-http-server + nokia e51 phone
On Mon, 2013-07-22 at 08:43 +0200, Patrick Ohly wrote:
> apparently the chunking cuts off events at fixed byte offsets -
in
this
> case between VER an SION so I would doubt that each chunkg is ever a
> valid xml on large syncs where multiple chunks are needed.
True, but that shouldn't be a problem for the parser. It has to deal
with getting data in chunks, it's normal. If it fails to parse, then
there is a bug in neon. Please send a full example, without truncating
and with the parser error message. If the data is too private, then
please send it do me directly - I promise to keep it confidential.
Thanks for the log.
This is very puzzling. The output shows that parsing resumes nicely
after receiving the latest chunk. It finishes the previous item
(end-element (1, {urn:ietf:params:xml:ns:caldav, calendar-data})), then
deals with getetag and prop, finally fails inside the status element.
There's nothing wrong with that element (or any other status element),
at least according to the earlier output.
The error comes from libxml2.so.2, parser.c, xmlParseCharDataComplex().
It seems to complain about a character of binary value 1, but I don't
see such a byte in the chunks dumped by neon.
Can you trigger this problem reliably?
The next step would be to run the parser under gdb and try to figure out
how it hits that error interactively. This will be difficult to do
unless I can somehow reproduce it :-(
--
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.