Bug#855096: unison: segfaults after connection has been established

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Bug#855096: unison: segfaults after connection has been established

Norbert Preining
Package: unison
Version: 2.48.3-1
Severity: grave
Justification: renders package unusable

Hi everyone,

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)

Hope that helps

Norbert

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.10.0-rc7 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages unison depends on:
ii  libc6  2.24-9

Versions of packages unison recommends:
ii  openssh-client [ssh-client]  1:7.4p1-6

Versions of packages unison suggests:
ii  unison-all  2.48+2

-- no debconf information

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Bug#855096: unison: segfaults after connection has been established

Stéphane Glondu-3
severity 855096 important
thanks

On 14/02/2017 02:07, Norbert Preining wrote:
> 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 (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.

Cheers,

--
Stéphane

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Processed: Re: Bug#855096: unison: segfaults after connection has been established

Debian Bug Tracking System
Processing commands for [hidden email]:

> severity 855096 important
Bug #855096 [unison] unison: segfaults after connection has been established
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
--
855096: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855096
Debian Bug Tracking System
Contact [hidden email] with problems

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Bug#855096: unison: segfaults after connection has been established

Norbert Preining
In reply to this post by Stéphane Glondu-3
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

Loading...