On Thu, 2010-04-08 at 05:46 +0100, Tino Keitel wrote:
On Thu, Apr 08, 2010 at 06:41:56 +0200, Tino Keitel wrote:
Maybe the stack strace is also useful, even without debugging symbols:
Program received signal SIGSEGV, Segmentation fault.
0x0000000100000000 in ?? ()
#0 0x0000000100000000 in ?? ()
#1 0x00007fffef163bad in XML_Parse () from /usr/lib/libxmlparse.so.1
#2 0x00007ffff5ee3455 in ?? () from /usr/lib/libsynthesis.so.0
#3 0x00007ffff5ee35ea in ?? () from /usr/lib/libsynthesis.so.0
#4 0x00007ffff5f402af in ?? () from /usr/lib/libsynthesis.so.0
#5 0x000000000056b20d in
#SyncEvo::SharedEngine::InitEngineXML(std::string const&) ()
#6 0x000000000050c7f4 in SyncEvo::SyncContext::initEngine(bool) ()
#7 0x000000000051eea9 in
#8 0x00000000004eef85 in SyncEvo::Cmdline::run() ()
#9 0x00000000004723f8 in Session::run() ()
#10 0x0000000000498fb0 in DBusServer::run() ()
#11 0x0000000000499692 in main ()
This is with SyncEvolution compiled from source, right? In order to
compile it, did you install the libsynthesis-dev pacckage (assuming that
you are on Debian or Ubuntu)? Which version of it?
I think Debian unstable and testing both have 18.104.22.168 as packaged with
SyncEvolution 1.0 beta 2. In any case, that doesn't explain the
In order to gather more information, can you also checkout
, then compile SyncEvolution again with
"--with-synthesis-src=<path to libsynthesis source> --disable-shared
--prefix=<some non-system dir> CFLAGS=-g CXXFLAGS=-g"?
After "make install" you can invoke <some
non-system-dir>/libexec/syncevo-dbus-server and it won't interfere with
your normal installation.
Do you still see the crash?
Does valgrind report anything useful?
Finally, we could also make a recent snapshot available as .deb. If it
works, we still won't know what the root cause was, though, so I'd
rather investigate the issue first.
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.