- edited description
orisync crashes
Issue #7
resolved
The orisync daemon does not appear to work on both my Arch 64 bit systems.
$ orisync
OriSync started as pid 14920
$ Signal Caught: 11
Backtrace:
[0] orisync() [0x465e7e]
[1] /usr/lib/libc.so.6(+0x35390) [0x7f87057ed390]
[2] orisync() [0x473993]
[3] /usr/lib/libpthread.so.0(+0x80a2) [0x7f87067940a2]
[4] /usr/lib/libc.so.6(clone+0x6d) [0x7f870589d3dd]
$ ori version
Ori Distributed Personal File System (Version 0.8.1) - Command Line Interface
Git Commit Id: fdf4f1595b39e118148ab2eb003bc84de8bbac6d
Build: RELEASE
Comments (8)
-
reporter
-
Can you provide me with more details of your system? Glibc version, compiler version, etc. Did you use the AUR?
Post the following files ~/.ori/orisyncrc but please replace your shared key with XXX ~/.ori/orisync.log
-
reporter
Yes, I used the AUR.
- clang version 3.3 (tags/RELEASE_33/final)
- glibc 2.18-12
Error occurs also with non existing ~/.ori
How do I tell Scons to compile with debugging symbols? Then I could be of more help.
In release 0.8.0 this error does not occur. But I could not get it to work either. Initialized orisync on both machines with same cluster name and key. Added on both machines the repo. On one machine --shallow replicated with ssh. I expected that now a change on one machine would be accessible "instantly" on the other machine. Am I wrong?
-
reporter
I've bisected the problem. The first commit where this crashes occures is
-
mokasin: enable debug symbols like so:
scons BUILDTYPE=DEBUG
(you'll also have to disable stripping in makepkg.conf)
-
Yes 9b61f0f appears to be the cause.
Anyways for everyone else you should probably be using the 0.8.0 release, but I will release 0.8.1 with a bunch of small bug fixes soon.
-
-
- changed status to resolved
Fixed
- Log in to comment
