On Mo, 2011-08-08 at 15:26 +0200, Tobias Hägele wrote:
> Am 2011-08-05 12:09, schrieb Patrick Ohly:
> > Then run the sync. You should see gdb telling you about a crash. Once
> > that happens, in gdb do:
> > # thread apply all bt
> >
> > What's the output?
> 
> #######################
> (gdb) run
> Starting program: /usr/libexec/syncevo-dbus-server
> [Thread debugging using libthread_db enabled]
> warning: the debug information found in 
> "/usr/lib/debug//usr/lib/libxml2.so.2.7.8" does not match 
> "/usr/lib/libxml2.so.2" (CRC mismatch).
> 
> warning: the debug information found in 
> "/usr/lib/debug/usr/lib/libxml2.so.2.7.8" does not match 
> "/usr/lib/libxml2.so.2" (CRC mismatch).

Hmm, that shouldn't happen if all of your system is up-to-date. Do you
have more obsolete packages installed?

> Program received signal SIGSEGV, Segmentation fault.
> g_variant_is_trusted (value=0x0)
>      at /build/buildd/glib2.0-2.28.6/./glib/gvariant-core.c:600
> 600   /build/buildd/glib2.0-2.28.6/./glib/gvariant-core.c: Datei oder 
> Verzeichnis nicht gefunden.
>       in /build/buildd/glib2.0-2.28.6/./glib/gvariant-core.c
> (gdb) thread apply all bt

That's way below SyncEvolution, inside libecal. I don't know why it
crashes. It doesn't look like something caused by SyncEvolution (NULL
pointer in g_variant_is_trusted()?!), but it can't be ruled out either.


> > Next repeat the exercise with syncevo-dbus-server started under
> > valgrind:
> > valgrind /usr/libexec/syncevo-dbus-server 2>&1 | tee /tmp/valgrind.log
> >
> > Does valgrind report any errors?
> 
> valgrind /usr/libexec/syncevo-dbus-server 2>&1 | tee /tmp/valgrind.log
[...]
> [ERROR] b_dbus_setup_bus() failed - server already running?

Can you redo this after killing the running syncevo-dbus-server?

-- 
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

Reply via email to