btsync coredumps on debian wheezy

[atte]

Hi

I'm getting started with btsync, but having some trouble. Things work as expected on my laptop (running crunchbang linux which is based on debian wheezy). However, when I ssh into my home server (running standard debian wheezy on a fit-pc), btsync coredumps with this dmp:

https://dl.dropboxus...c4-09233513.dmp

As far as I can tell the two environments should be quite identical, but obviously I missed something.

Any suggestions or hints would be appreciated :-)

[kos13]

Seems like a wrong dmp, it is only 440 bytes

[atte]

Seems like a wrong dmp, it is only 440 bytes

Hi

Well, that's the dump I got.

It seems the glibc 2.3 version is working just fine on the debian box, although I don't get why (as far as I can tell glibc is version 2.13):

atte@vodskov:~$ /lib/i386-linux-gnu/libc.so.6
GNU C Library (Debian EGLIBC 2.13-38) stable release version 2.13, by Roland McGrath et al.
Copyright (C) 2011 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 4.4.7.
Compiled on a Linux 3.2.35 system on 2012-12-30.
Available extensions:
crypt add-on version 2.1 by Michael Glad and others
GNU Libidn by Simon Josefsson
Native POSIX Threads Library by Ulrich Drepper et al
BIND-8.2.3-T5B
libc ABIs: UNIQUE IFUNC
For bug reporting instructions, please see:
<http://www.debian.org/Bugs/>.

[rdebath]

Um; I think the MDMP file you've posted is a Windows dump file; can't tell for sure though because it is empty, just a header.

Debian is usually setup with core dumps disabled ie:

$ ulimit -c
0
$

You need to enable them before you'll get a linux core dump ...

$ ulimit -c unlimited
$ ulimit -c
unlimited
$

This only applies to the shell you run the ulimit command on.

[atte]

You need to enable them before you'll get a linux core dump ...

$ ulimit -c unlimited
$ ulimit -c
unlimited
$

Thanks for the info!

Would you (devs) like to get a fresh dump, or is it irrelevant now?

[atte]

Ok, btsync is not running well at all on that box.

The i386 version exits after about 10 seconds with this dump:

https://dl.dropboxusercontent.com/u/4343030/4380f07d-14dc-c68e-47b5b7b7-70802820.dmp

https://dl.dropboxusercontent.com/u/4343030/core

The glibc 2.3 version (although it shouldn't fit my system), runs up a bit longer, about 2 minutes, syncing seems to be working, then it exits just like that, no dump, no nothing. I have no idea where to go from here :-(

A bit about my system (debian wheezy on a fit-pc):

atte@vodskov:~$ ulimit -c
unlimited

atte@vodskov:~$ uname -a
Linux vodskov 3.2.0-4-486 #1 Debian 3.2.41-2+deb7u2 i586 GNU/Linux

atte@vodskov:~$ ll /lib/i386-linux-gnu/libc.so.6
lrwxrwxrwx 1 root root 12 May 26 15:33 /lib/i386-linux-gnu/libc.so.6 -> libc-2.13.so

atte@vodskov:~$ /lib/i386-linux-gnu/libc.so.6
GNU C Library (Debian EGLIBC 2.13-38) stable release version 2.13, by Roland McGrath et al.
Copyright (C) 2011 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 4.4.7.
Compiled on a Linux 3.2.35 system on 2012-12-30.
Available extensions:
crypt add-on version 2.1 by Michael Glad and others
GNU Libidn by Simon Josefsson
Native POSIX Threads Library by Ulrich Drepper et al
BIND-8.2.3-T5B
libc ABIs: UNIQUE IFUNC
For bug reporting instructions, please see:
<http://www.debian.org/Bugs/>.

Btsync is running just fine on my laptop running crunchbang linux. Needles to say, I'd really appreciate any pointers, and would be more than happy to supply any info that could help track this down.

[atte]

Seems like a wrong dmp, it is only 440 bytes

You'll find links to full core dump in this thread.

I also send you a PM with links to two sync.log files created with debug turned on.

[atte]

If I run with option --nodaemon both versions terminate with

Illegal instruction

NB: This is with version 1.1.27

[rdebath]

Sounds like your "geode" processor doesn't have enough features for the compile options they use.

$ cat /proc/cpuinfo

kos13 do they compile with an "--march=i686" option ? That might cause this.

Though if the old machine version isn't compiled the same that might imply an OpenSSL bug or a bug in your selection of acceptable encryption/hashing modules.

NB: I still want a version to run on my woody machine ie: i486 static ELF.

[atte]

cat /patte@vodskov:~$ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 5
model  : 10
model name : Geode(TM) Integrated Processor by AMD PCS
stepping : 2
microcode : 0x8b
cpu MHz  : 499.887
cache size : 128 KB
fdiv_bug : no
hlt_bug  : no
f00f_bug : no
coma_bug : no
fpu  : yes
fpu_exception : yes
cpuid level : 1
wp  : yes
flags  : fpu de pse tsc msr cx8 sep pge cmov clflush mmx mmxext 3dnowext 3dnow
bogomips : 999.77
clflush size : 32
cache_alignment : 32
address sizes : 32 bits physical, 32 bits virtual
power management:

Ok, so I'm hoping for a binary compatible with my CPU...

Silly problem, actually, if btsync were open-source, I could just go ahead and compile a working binary myself.

[dirkhas]

Any news on this? I've got the same problem (running Ubuntu Lucid on an identical fitPC / Geode / i586 machine) - both i386 and i386-glibc2.3 versions crash with "Illegal Instruction", the former right away, the latter after one or two minutes.

Will there be a version compiled for i586?