Bug#855096: unison: segfaults after connection has been established
Hi Stéphane,
> > 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
checking everything.
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.
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. + JAIST + TeX Live + Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Reply to: