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

Milan Crha mcrha at redhat.com
Wed Feb 22 07:20:28 UTC 2023


On Tue, 2023-02-21 at 14:55 -0500, Max Pyziur wrote:
> ==43163== Process terminating with default action of signal 11
> (SIGSEGV): 
> dumping core
> ==43163==    at 0x51A4E5C: __pthread_kill_implementation 
> (pthread_kill.c:44)
> ==43163==    by 0x5154A75: raise (raise.c:26)
> ==43163==    by 0x5154B1F: ??? (in /usr/lib64/libc.so.6)
> ==43163==    by 0x5819D6F: ??? (in /usr/lib64/libcurl.so.4.8.0)

	Hi,
I believe you can stop trying to get a better backtrace from valgrind,
because valgrind did not notice any wrong thing, it only provides a
backtrace for the SIGSEGV, the same as you already provided from the
gdb here:
https://lists.freedesktop.org/archives/syncevolution/2023-February/000778.html
which, interestingly, contains almost all the debug symbols from the
libcurl.

Patrick, I know it's obvious, but just in case, I switched
SyncEvolution to build against libcurl, instead of libsoup, in Fedora
to "get rid of" the problem with transition from libsoup2 to libsoup3.

I created a free account for the memotoo site and I can reproduce it
too. I filled a Fedora bug for it:
https://bugzilla.redhat.com/show_bug.cgi?id=2172377

Please, see it for any further updates. If there's needed any change on
the SyncEvolution side I'll pass it over to this thread.

	Bye,
	Milan



More information about the SyncEvolution mailing list