« Return to Thread: Issue with r5507

Re: Issue with r5507

by Daniel Gollub-2 :: Rate this Message:

Hi Nicolas,

On Wednesday 01 April 2009 07:54:45 pm Nicolas wrote:
[...]

> I have updated my repository copy with the last revision r5507.
>
> I post my issue... I don't still seek to understand this issue :
>
>
> contact sink of member 2 of type barry-sync just connected
> Main sink of member 2 of type barry-sync just connected
> All clients connected or error
> contact sink of member 1 of type evo2-sync just sent all changes
> Main sink of member 1 of type evo2-sync just sent all changes
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0xb2dd5b90 (LWP 13100)]
> 0xb7f0539d in osync_queue_send_message_with_timeout (queue=0x11,
> replyqueue=0x0, message=0x809dfd8,
> timeout=0, error=0xb2dd5098)
> at /usr/local/src/opensync/opensync/opensync/ipc/opensync_queue.c:1382
> 1382 if (queue->cmd_queue) {

I could imagine the address of pointer queue is not valid -> 0x11 ?!!

[...]

> (gdb) backtrace
> #0 0xb7f0539d in osync_queue_send_message_with_timeout (queue=0x11,
> replyqueue=0x0, message=0x809dfd8,
> timeout=0, error=0xb2dd5098)
> at /usr/local/src/opensync/opensync/opensync/ipc/opensync_queue.c:1382
> #1 0xb7f056ae in osync_queue_send_message (queue=0x11, replyqueue=0x0,
> message=0x809dfd8,
> error=0xb2dd5098)
> at /usr/local/src/opensync/opensync/opensync/ipc/opensync_queue.c:1375
> #2 0xb7ed85fd in _osync_client_get_changes_callback (data=0x808f170,
> error=0x0)
>
> at /usr/local/src/opensync/opensync/opensync/client/opensync_client.c:286
> #3 0xb7f0c9fb in osync_context_report_success (context=0x80db4b8)
>
> at /usr/local/src/opensync/opensync/opensync/plugin/opensync_context.c:132
> #4 0xb6f4f182 in contact_get_changes (sink=0x8088980, info=0x808b728,
> ctx=0x80db4b8, slow_sync=1,
> userdata=0x808cd20) at barry_sync.cc:591

[...]

Strange - i wonder how the process was able to manage to walk the long way
till get_changes() call till the client->outgoing got malformed.

Could you try to just sync with evo2-sync and file-sync and barry-sync and
file-sync - in separated groups! To check if this is the fault of one plugin
or really an engine issue.

Also helpful might be:
G_SLICE=always-malloc valgrind osynctool --sync your-evo2-and-barry-group

Best Regards,
Daniel

------------------------------------------------------------------------------
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel

« Return to Thread: Issue with r5507