[SyncEvolution] Syncing to Memotoo w SyncEvolution post-Fedora 37 upgrade (fwd)
Max Pyziur
pyz at brama.com
Sat Feb 18 23:34:24 UTC 2023
On Sat, 18 Feb 2023, Patrick Ohly wrote:
> Max Pyziur <pyz at brama.com> writes:
>> This message also needed to go to the list.
>
> This points towards memory corruption in the transfer buffers:
>
>>> coredumpctl debug 65192
>>
>> <deleting output until (gdb) prompt>
>>
>>
>> (gdb) bt
>> #0 0x00007f28c1252d70 in () at /lib64/libcurl.so.4
>> #1 0x00007f28c12278ed in Curl_fillreadbuffer (data=data at entry=0x562766d4c960,
>> bytes=<optimized out>, nreadp=nreadp at entry=0x7ffc403dba50) at
>> ../../lib/transfer.c:235
>
> But it remains unclear where that comes from. What you can try next is
> running syncevo-dbus-server under valgrind. Remember where the binary
> is, kill the running process, then in a console window run `valgrind
> <path to the binary>/syncevo-dbus-server`.
There is no binary on my machine called syncevo-dbus-server.
I ran the command
dnf whatprovides syncevo-dbus-server
and it produces no results.
> In another window run the sync command.
A housekeeping request: you've given me instructions as to how find useful
output for you to debug this problem. Thank you.
However, it does get a little muddled at times because of the
asynchronicity: a set of instructions, and then another later. It becomes
difficult to judge if all of the instructions need to be run in sequence,
or just the most recent suggestion.
But thanks again, and hopefully, this will be resolved.
Max
pyz at brama.com
More information about the SyncEvolution
mailing list