On Thu, 2011-12-01 at 14:26 +0100, Chris Kühl wrote:
On Thu, Dec 1, 2011 at 11:32 AM, Patrick Ohly
> I've changed the automatic testing so that syncevo-dbus-server is
> started under valgrindcheck.sh by test-dbus.py. This revealed some minor
> memory leaks and broken memory accesses (typically read after free). I
> I've fixed all of that, see master branch.
Unfortunately it did not run as smooth as I'd like to. The checking of
Python 2.7 unittest output still had some issues, which hid some test
failures. It seems that running under valgrind still skews the timing
enough to cause some test failures.
When it fails, I see issues with syncevo-dbus-server not being able to
restart because allegedly the org.syncevolution name is taken. This
could be related to killing the "valgrindcheck.sh" wrapper process
instead of the "syncevo-dbus-server" process.
Killing the process group of the started process might help. Need to
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.