Re: [Opensync-devel] python wrapper and plugin

[Chris F. <cd...@fo...>]

On Thu, Aug 02, 2012 at 03:27:04PM +0100, Mark Ellis wrote:
> You can reproduce it wonderfully with the test module included with the
> python plugin, which is what i have mostly been using, it's a lot
> simpler to deal with.

Thanks!  Mine is crashing in a different place, but it is related to
osync_list_copy() / osync_list_free(), and according to my valgrind runs,
I'm starting to wonder if somehow Python's malloc system is being used
by opensync.  The errors I'm getting are pretty weird, and valgrind
seems to have lost track of where the memory came from.

This is early results, so clarity may come later. :-)

Maybe you can run valgrind on yours and see if it gives us any clues?

Here's a sample command similar to what I'm using:

	valgrind --log-file="py-%p.log" --trace-children=yes --leak-check=full --track-origins=yes osynctool --discover pytest


> Also attached 3 patches, api_change.diff is self explanatory,
> opensync1.diff tweaks it to work against the module built by your git
> tree, and buildsys.diff fixes it to use your git cmake modules, pass
> -DCMAKE_MODULE_PATH=<path> to cmake to build it. Haven't applied them in
> svn 'cos it didn't make much sense to do so, but if you want to import
> it into git with the patches ....

If I can get this working, I'll create a git repo for the python plugin
as well.

I've included your api_change.diff and opensync1.diff patches.  The
buildsys.diff fixes were already in my copy.

Thanks,
- Chris