On Monday 6 January 2025 10:52:18 Greenwich Mean Time Filip Milosavljević wrote:

Greetings everyone, glad to finally be part of the club.

Welcome! :-)

I've setup neomutt with Gmail successfully but iSync is giving me pains.
I've enabled all use flags :

net-mail/isync berkdb sasl ssl zlib

Setup .mbsyncrc as follows : https://bpa.st/FCFQ

and my isync.gpg as follows : https://bpa.st/LRFA

All of these were the result of following the following article :

https://seniormars.com/posts/neomutt/#isync

It worked for me when I was on Fedora, and I had no segfaults or
whatever on there (though isync was a bit of a pain to setup there as
well).

With all this in mind, here's the output in full :

[N] ficonni@tux ~> mbsync -a
C: 0/1 B: 0/0 F: +0/0 *0/0 #0/0 N: +0/0 *0/0 #0/0fish: Job 1, 'mbsync -a' terminated by signal SIGSEGV (Address boundary error)

Doing the same in bash will result in :

ficonni@tux ~ $ mbsync -a
C: 0/1 B: 0/0 F: +0/0 *0/0 #0/0 N: +0/0 *0/0 #0/0Segmentation fault

I've also double-checked if ~/.local/share/email/ficonni exists, and it
does.

I've tried searching for similar issues online but found nothing.

This kind of error occurs when a program is trying to access memory space not allocated to it.

I've also contacted #gentoo but they agreed this was only a segfault and
that my configs were good. It would need debugging they said but I didn't have the time to work on it anymore then and the issue still stands so here
I am.

Any help please ?

-------------------
Filip Milosavljević

Sadly without a backtrace to indicate which software makes a call to unallocated memory space, it is difficult to guess what causes the problem and how to fix it.

You could take a look here for more information on debugging such faults, when you have more time:

https://wiki.gentoo.org/wiki/GDB https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces https://wiki.gentoo.org/wiki/Valgrind

If your problem is caused by a frequently encountered bug, you'll find it is fixed sooner or later. Otherwise, for some edge case you may have come across, you'll have to submit a bug report with necessary debugging information.

PS. I recall wget causing segfaults when built against some version of glibc, which was patched soon after a bug report. When such errors are widespread and bug reports by users arrive thick and fast, a patch or workaround soon arrives.

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmd7xGIACgkQseqq9sKV Zxlz8RAAi6IMlok5bWd9R8zHRnQNvB58rFxdoCUpJWgsyCLKFRVR8Z5XzeoRy0hZ 0s49oitubMavOIlKpfCcoi0ok4j4g7xMUTe9P9sxHz57Z+Udb1Cj9c1HnymMtSNl d0hkk8UKJSzgeTb5mIfMI3wJtPr+v3ogY4SsYziMmdf/c4CryECr3Q3EkcO/pSGx uWLPjN0/3PiQh+ojE5Y8vsUfY0p3oOG+T/ssyVkwO4yfQFN3wBq2V4HCnD1v3xR0 ucETCZVSDuvqtGKLYKOTyR/Ew/BkbGmWS2I6B9XO1A+EUzHRU21p/zSIzgfNdYoy gZgICbtB/f4IL2ctEl1R/BoFGmar7CdBCsREUv+vqp0dn/dgO6oZbhgZt6WaZ+ve DzTE9f8bToRsYPgi5NiWYt5Z/oWFGXULBSmOW22l8qayQqDaIEKpUDpEAsDsuv3Q CHL8tNJBpqr3u7PI3Txo0t/B1keF6ijh6OkM4el9s7nB8nmgj1sd921pkpjkrwRt q/PYGYwTeTyEJ712WqEeEr6ajh8G35r0yxvjmFqOxVoaMHXeCWyTCVbNtZHip2jf D64HKVjMewH15CtEMrGV0avmXuHk6Eel/DAkXTjSzpbycXtH0yOBt4zbLdO1uGqY 7q9m7oz0VY4FBwloovxGuhyMRLno488nNfFHUdrgWwG+h2ATfw8=
=k7w8
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)