On Fri, 2013-09-27 at 21:14 +0200, Tino Keitel wrote: > On Fri, Sep 27, 2013 at 16:50:01 +0200, Patrick Ohly wrote: > > On Fri, 2013-09-27 at 16:03 +0200, [email protected] > > wrote: > > > On Fri, Sep 27, 2013 at 08:35:10 +0200, Patrick Ohly wrote: > > > > > > [...] > > > > > > > Looks related to handling a D-Bus message. Can you run sync-ui as > > > > > > > > env G_DBUS_DEBUG=message valgrind sync-ui > > > > > > > > and check what the last message is? valgrind should give more > > > > information about the crash. > > > > > > Hi, > > > > > > attached is the complete output of the above command. > > > > I need the output when it crashes. > > It doesn't crash when run under valgrind.
Let's backtrace a bit. What steps are necessary to make it crash without valgrind? And those same steps do not cause it to crash when running under valgrind? -- 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] https://lists.syncevolution.org/mailman/listinfo/syncevolution
