Btsync 1.4.72 Crash On Linux I386

[fastfwd]

When starting BTSync 1.4.72 on a Debian box which had previously been running version 1.3.106 with no errors, I get:

symbol lookup error: /usr/local/bin/btsync/btsync: undefined symbol: _ZNSs4_Rep20_S_empty_rep_storageE

Perhaps there's some library that's not being properly linked?

 

[vadimt]

Thanks for reporting!

We will try to repro it in our lab and fix it asap.

Could you please provide your linux version?

Thanks!

[b0rman]

Same problem!

Centos 6.5 x86

[nop]

I think that in output of "ldd btsync" you will find that some libs are missing. 

 

May help:

 

1. "pidof btsync"

2. "export `cat /proc/PIDOF_VALUE/environ | strings | grep LD_LIBRARY_PATH`"

[jvavruska]

Same on QNAP TS-290. All company synchronization is now busted. Shame!

[fearedbliss]

To narrow this down, this is working fine on my Gentoo Linux x86_64 machine (I don't have a i386 system so can't repro)

 

Info:

 

lddtree output:

jon@octopus ~ $ lddtree /opt/btsync/btsyncbtsync => /opt/btsync/btsync (interpreter => /lib64/ld-linux-x86-64.so.2)    librt.so.1 => /lib64/librt.so.1    libcrypt.so.1 => /lib64/libcrypt.so.1    libdl.so.2 => /lib64/libdl.so.2    libm.so.6 => /lib64/libm.so.6    libpthread.so.0 => /lib64/libpthread.so.0    libc.so.6 => /lib64/libc.so.6    ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2

compiler, glibc versions:

gcc-4.7.3, glibc-2.19-r1

uname output:

jon@octopus ~ $ uname -aLinux octopus 3.14.17-KS.01 #8 SMP PREEMPT Thu Aug 14 23:45:41 EDT 2014 x86_64 AMD FX(tm)-8120 Eight-Core Processor AuthenticAMD GNU/Linux

[andrewb]

Same problem!

Centos 6.5 x86

 

Also same on older Centos 5.9

 

As per fearedbliss. I have the following info for my i386 install

 

lddtree output (current 1.4 and older 1.3 versions):

#ldd btsync-1.3.94        linux-gate.so.1 =>  (0x003b2000)        librt.so.1 => /lib/librt.so.1 (0x007c1000)        libdl.so.2 => /lib/libdl.so.2 (0x00ccd000)        libm.so.6 => /lib/libm.so.6 (0x0055c000)        libpthread.so.0 => /lib/libpthread.so.0 (0x00bd8000)        libc.so.6 => /lib/libc.so.6 (0x00a79000)        /lib/ld-linux.so.2 (0x00657000)# ldd btsync-1.4.075        linux-gate.so.1 =>  (0x00605000)        librt.so.1 => /lib/librt.so.1 (0x007c1000)        libcrypt.so.1 => /lib/libcrypt.so.1 (0x07660000)        libdl.so.2 => /lib/libdl.so.2 (0x00ccd000)        libm.so.6 => /lib/libm.so.6 (0x0055c000)        libpthread.so.0 => /lib/libpthread.so.0 (0x00bd8000)        libc.so.6 => /lib/libc.so.6 (0x00a79000)        /lib/ld-linux.so.2 (0x00657000)

compiler, glibc versions:

gcc-4.1.2, glibc-2.5-107

uname output:

# uname -aLinux nexus.cnf.com.au 2.6.18-348.4.1.el5 #1 SMP Tue Apr 16 16:02:56 EDT 2013 i686 i686 i386 GNU/Linux

[andrewb]

On the 1.4.75 (i386) Crash On Readynas Pro thread, @cjvs, on 15 Sept 2014 - 05:10 AM, said:

 

I got the same issue on a QNAP TS-259 PRO+ with version 4.1.0.. However, I initially downloaded the i386 version, and later retried with the linux i386(glibc 2.3) version which did not give me this error (and could start).

 

 

 

This seems to work OK for my Centos 5.9 i386 install.

I have glibc-2.5-107 on that machine and have always used the non glibc23 compile of btsync without a problem.  

 

Does this mean the glib23 compile is now needed for glibc >= 2.3.  It may explain why @fearedbliss has it running fine on Gentoo x86_64 (he has glibc-2.19-r1).