since short time unison (gtk and text mode) is crashing with
sigsegv after the connection has been started.
Core was generated by `unison bulldog-home'.
Program terminated with signal SIGSEGV, Segmentation fault.
gdb didn't help as there is no debug package neither in the normal archives
nor in the debug-sid archive.
Calling unison with -debug all I get at the end:
[update] Loading archive from /home/norbert/.unison/arf0168c12ac8c1cc3e65ee115fd63d9b3
[server: update] Loading archive from /home/norbert/.unison/ar40f7a1363152c2a5aa375f92b6e8fd18
Growing heap to 700852k bytes
Growing page table to 2048 entries
Growing page table to 4096 entries
Growing page table to 8192 entries
Growing page table to 16384 entries
Growing page table to 32768 entries
Growing page table to 65536 entries
Growing page table to 131072 entries
Growing page table to 262144 entries
[server: update] Setting archive for //bulldog//home/norbert
[server: remote] Connection closed by the client
Segmentation fault (core dumped)
> > since short time unison (gtk and text mode) is crashing with
> > sigsegv after the connection has been started.
> What are the versions (and origin) of unison used at each endpoint? Can you
> reproduce the bug easily?
I *could* reproduce it even after a few reboots, but due to proper need
I have reverted to removing the cache files and let unison restart
THis was again a problem (ok, I am syncing a few hundred GB), as unison
has a very common tendency to just simply die, repeatedly.
I realized from iterated repeating that single *BIG* directories are
very prone to kill unison, while if I pre-populate the directory
hierarchy and each file is considered by itself, unison continues
without any problem despite the big amount of data transfered.
(So wild guess: some memory leak or other problem with big directories)
> I (and others) routinely run Unison 2.48.3-1 (on both ends) and I've never
> seen this bug. Since this bug doesn't seem to happen everywhere, I downgrade
> the severity to important.
I am using the latest versions available in Debian/sid, updated daily.
I tried to search for debug symbols, but there aren't any as far as I see,
so I am having a hard time debugging it.
If you have a suggestion how to debug it, please let me know.