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.
signature.asc
Description: This is a digitally signed message part.
