[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:
>> 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":

Shell #1
Output:
pyz at pegasus ~> killall syncevo-dbus-server
syncevo-dbus-server: no process found
pyz at pegasus ~>

Shell #1
Output:
pyz at pegasus ~> valgrind --leak-check=full /usr/libexec/syncevo-dbus-server
==24276== Memcheck, a memory error detector
==24276== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==24276== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright 
info
==24276== Command: /usr/libexec/syncevo-dbus-server
==24276==



Shell #2
pyz at pegasus ~> syncevolution --run  --sync refresh-from-local memotoo
[INFO] memo: inactive
[INFO] todo: inactive
[ERROR] The connection is closed
pyz at pegasus ~>



Shell #1
--24276-- WARNING: unhandled amd64-linux syscall: 434
--24276-- You may be able to write your own handler.
--24276-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24276-- Nevertheless we consider this a bug.  Please report
--24276-- it at http://valgrind.org/support/bug_reports.html.

... and then it hangs.


fyi,

MP
pyz at brama.com