Re: [Opensync-devel] python wrapper and plugin

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

On Wed, Aug 01, 2012 at 08:48:29PM +0100, Mark Ellis wrote:
> We do have a prototype plugin for the 0.40 branch, using the python
> plugin. However, i get a segfault during the discover phase, in
> osync_list_copy, with the glib slice allocator returning an evidently
> invalid address.
> 
> It's all got a bit beyond me, I'm afraid. I can't see anything obviously
> wrong, i thought it might be something wierd with glib thread initialisation,
> but after putting checks in all kinds of places i can't find it. Does anyone
> have any ideas ? I'm starting to think it'll just be easier to re-write the
> plugin in C.

I vaguely remember you reporting this before, so I'm glad you're tackling
it again!  Hopefully I can help a bit more this time.

Do you have a backtrace of the segfault?

I don't have any windows mobile devices to test with.  What would be a
good way to reproduce this error without your plugin?  Or do you not need
a device plugged in, in order to reproduce?

Thanks,
- Chris