On Tue, 2011-10-25 at 13:41 +0200, Frederik Elwert wrote:
> >> 2. On my work machine, where I am still running Ubuntu Lucid, the
> >> syncevo-dbus-server fails silently. I could manage to sync using
> >> "--daemon=no", but for everyday use s-d-s is more comfortable.
> >>
> >> While you probably cannot do much about #1, it might be worth looking
> >> at #2.
> >
> >Absolutely.
> >
> >> I attached the terminal output of both s-d-s and syncevolution,
> >> though it does not tell very much. Which additional information do you
> >> need?
> >
> >Please run syncevo-dbus-server under gdb and when it crashes (which I
> >assume it will), run "thread apply all bt".
>
> I did and will send you the log in private.
SIGPIPE is triggered, apparently by a writev() inside libdbus.
SyncEvolution doesn't do anything with SIGPIPE. I wonder whether libdbus
expects that the process ignores it. The gdbus example does that.
Can you compile a test executable which adds the following lines to
SyncContext.cpp SyncContext::initMain()?
struct sigaction sa;
memset(&sa, 0, sizeof(sa));
sa.sa_handler = SIG_IGN;
sigaction(SIGPIPE, &sa, NULL);
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
