Joe Orton <joe@manyfish.co.uk> writes:
> I can't reproduce the error message, but I do notice you're using
> libxml2. If I build neon against libxml2 rather than expat I can
> reproduce the seemingly random insertion of newlines in the log messages
> (packet fragmentation affects the size of the blocks passed to XML
> parser so that could be the random factor).
Interesting. I wonder if I've been getting these extra bits all
along. I've probably been building with libxml2 on that machine (my
home machine, a Debian GNU/Linux box) for a long time.
> With expat the log messages are identical every time, so there is
> probably a bug either in libxml2 or in how neon drives it.
>
> Can you upload the neon debug log somewhere (with e.g. neon-debug-mask =
> 134) from a run which produces the error?
Now I cannot reproduce the error anymore, with Neon 0.24.6. And the
logs produced don't seem to have content problems, either -- at least,
not in the revisions that had problems before. I'm building with
0.24.7 now, will report results either way.
By the way, in an earlier mail I wrote a Neon version number as
"0.26", when I meant "0.24.6", of course.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 6 18:36:14 2004