[Csync2] Format error while receiving data after segfault

[Art -kwaak- van Breemen]

On Tue, Dec 09, 2008 at 01:27:32PM +0100, Lars Ellenberg wrote:
> if you have the core file already,
> ask for a backtrace: bt

Heh...
It's a bit hard to trace:
ard at nathalie:/var/log$ sudo zgrep csync2 kern.log*
kern.log.20080907064705.gz:Sep  5 21:55:02 localhost kernel: csync2[13519:#0]: segfault at 0000000000000046 rip 00000000f7dfe7a7 rsp 00000000ffcbc650 error 4
kern.log.20081109064707.gz:Nov  4 10:52:18 localhost kernel: csync2[29650:#0]: segfault at 0000000000000046 rip 00000000f7dc77a7 rsp 00000000ff9eb370 error 4
kern.log.20081123064708.gz:Nov 20 10:33:25 localhost kernel: csync2[10436:#0]: segfault at 0000000000000046 rip 00000000f7e277a7 rsp 00000000ffdacf00 error 4
kern.log.20081130064708.gz:Nov 24 15:01:52 localhost kernel: csync2[9416:#0]: segfault at 0000000000000046 rip 00000000f7e057a7 rsp 00000000ffcd5620 error 4
kern.log.20081207064712:Nov 30 10:32:35 localhost kernel: csync2[8648:#0]: segfault at 0000000000000046 rip 00000000f7dc37a7 rsp 00000000ff9502a0 error 4
kern.log.20081207064712:Dec  3 08:57:42 localhost kernel: csync2[2877:#0]: segfault at 0000000000000046 rip 00000000f7dec7a7 rsp 00000000fff34080 error 4

For me this means that 1 out of 1M invocations crashes.
If anybody can make a testcase for it, I can try to fix it.
I only do:
csync2 -h <up to 20 files>, csync2 -l 1000 -B -A -c -v and csync2 -l 1000 -B -A -u -v
The first question is: which of these variants crashes.

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in email?