Hello all,
At last. I think I have finally tracked down the cause of these random
and seemingly untraceable segfaults, 'broken pipe' messages, and sudden
exitting of the sync process when used with dbus >= 0.80. It turns out
that the dbus main loop is not thread-safe unless a function is called
to initialize it. Sane enough, but although this function is buried in
the dbus-python API docs, no mention of its requirement in a
multithreaded environment is clearly stated anywhere else. Least of all
the dbus-python tutorial..... Aaarrgh!
So, could anyone who is running a current sync-engine with either
dbus-python < 0.80 and dbus-python > 0.80 please update from SVN and
test. I have tested this with dbus-python 0.82 on a 64 bit system, but
it would be great to know if it performs correctly on 32 bit systems.
Shouldn't make any difference, but you never know....
Also, I can't test with dbus-python < 0.80 as I no longer have it on my
development box. I have added code to ensure that the sync-engine plugin
should now work with both versions, but this new code is untested on
these old versions of dbus-python. If possible, could someone please
confirm that I haven't broken support for these older versions?
Have fun,
John.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel
