[SyncEvolution] Syncing to Memotoo w SyncEvolution post-Fedora 37 upgrade (fwd)

[Max Pyziur]

On Tue, 21 Feb 2023, Patrick Ohly wrote:

> Max Pyziur <pyz at brama.com> writes:
>
>> On Tue, 21 Feb 2023, Patrick Ohly wrote:
>>
>>> Max Pyziur <pyz at brama.com> writes:
>>>> I'm following the steps that you've given me, as best I understand them.
>>>> Here, I've enumerated them (1 to 4).
>>>
>>> Something must have gone wrong, otherwise you wouldn't have gotten the
>>> "could not obtain D-Bus name" error. Let's try again.
>>>
>>> In one shell, run:
>>>  killall syncevo-dbus-server
>>>  valgrind --leak-check=full /usr/libexec/syncevo-dbus-server
>>>
>>> It should remain running now, without "could not obtain D-Bus name".
>>>
>>> In another shell:
>>>  syncevolution --run  --sync refresh-from-local memotoo
>>>
>>> Now, and not sooner, should the original shell show additional
>>> output. What I expect there is information about memory corruption or
>>> the segfault.
>>>
>>
>>
>> Here's the output; the seeming exception is "WARNING: unhandled
>> amd64-linux syscall: 434":
>
> No, that's just a warning.
>
>> pyz at pegasus ~> syncevolution --run  --sync refresh-from-local memotoo
>> [INFO] memo: inactive
>> [INFO] todo: inactive
>> [ERROR] The connection is closed
>
> Somehow syncing failed without triggering the segfault. But I don't know
> which connection is meant here.
>
> Let's try something simpler. syncevolution works without the DBus
> server. Try this please:
>
> valgrind syncevolution --daemon=no --run --sync refresh-from-local memotoo

I first killed any existing processes as a precaution:
pyz at pegasus ~>  killall syncevo-dbus-server
syncevo-dbus-server: no process found
pyz at pegasus ~>


and then ran the valgrind command as indicated
pyz at pegasus ~> valgrind syncevolution --daemon=no --run --sync 
refresh-from-local memotoo
==28498== Memcheck, a memory error detector
==28498== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==28498== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright 
info
==28498== Command: syncevolution --daemon=no --run --sync 
refresh-from-local memotoo
==28498==
[INFO] memo: inactive
[INFO] todo: inactive
==28498==
==28498== Process terminating with default action of signal 11 (SIGSEGV): 
dumping core
==28498==    at 0x51A4E5C: __pthread_kill_implementation 
(pthread_kill.c:44)
==28498==    by 0x5154A75: raise (raise.c:26)
==28498==    by 0x5154B1F: ??? (in /usr/lib64/libc.so.6)
==28498==    by 0x5819D6F: ??? (in /usr/lib64/libcurl.so.4.8.0)
==28498==    by 0x1FFEFFDB23: ???
==28498==    by 0x1FFEFFDB1C: ???
==28498==    by 0xDDD2467BF7667EFF: ???
==28498==    by 0xC09539F: ???
==28498==    by 0xB51851F: ???
==28498==    by 0x5818733: ??? (in /usr/lib64/libcurl.so.4.8.0)
==28498==
==28498== HEAP SUMMARY:
==28498==     in use at exit: 20,196,346 bytes in 202,639 blocks
==28498==   total heap usage: 847,616 allocs, 644,977 frees, 144,844,326 
bytes allocated
==28498==
==28498== LEAK SUMMARY:
==28498==    definitely lost: 48 bytes in 1 blocks
==28498==    indirectly lost: 774 bytes in 22 blocks
==28498==      possibly lost: 16,960 bytes in 12 blocks
==28498==    still reachable: 20,018,188 bytes in 201,272 blocks
==28498==                       of which reachable via heuristic:
==28498==                         newarray           : 6,936 bytes in 195 
blocks
==28498==         suppressed: 0 bytes in 0 blocks
==28498== Rerun with --leak-check=full to see details of leaked memory
==28498==
==28498== For lists of detected and suppressed errors, rerun with: -s
==28498== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Segmentation fault (core dumped)
pyz at pegasus ~>