[gentoo-user] Re: Subject: Digest of gentoo-user@lists.gentoo.org issue 4066 (205256-205258)

[gentoo-user] Re: Subject: Digest of gentoo-user@lists.gentoo.org issue 4066 (205256-205258)

[Filip Milosavljević]

[-- Attachment #1: Type: text/plain, Size: 4006 bytes --]

On Sat, Jan 11, 2025 at 02:32:08PM +0000, gentoo-user+help@lists.gentoo.org wrote:
>Topics (messages 205256 through 205258):
>
>[gentoo-user] 'mbsync -a' terminated by signal SIGSEGV (Address boundary error)
>      205256 - Filip Milosavljević <ficonni64@gmail.com>
>
>[gentoo-user] 'mbsync -a' terminated by signal SIGSEGV (Address boundary error)
>      205257 - Michael <confabulate@kintzios.com>
>
>[gentoo-user] update catch-22 with Wifi
>      205258 - Frank Steinmetzger <Warp_7@gmx.de>
>

>Date: Mon, 6 Jan 2025 11:52:18 +0100
>From: Filip Milosavljević <ficonni64@gmail.com>
>To: gentoo-user@lists.gentoo.org
>Subject: [gentoo-user] 'mbsync -a' terminated by signal SIGSEGV (Address
> boundary error)
>
>Greetings everyone, glad to finally be part of the club.
>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.
>
>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ć



>Date: Mon, 06 Jan 2025 11:54:10 +0000
>From: Michael <confabulate@kintzios.com>
>To: gentoo-user@lists.gentoo.org
>Subject: Re: [gentoo-user] 'mbsync -a' terminated by signal SIGSEGV (Address
> boundary error)
>
>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!  :-)
>
>

Thank you ! 

>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.

I've taken a quick  look at the GDB page and will look at the others as well.
Only thing I have to add are :

1. The Gentoo Wiki is exceptionaly well written, some that's not in IT 
like me understood what was written rather well regardeless of the
topic.

2. We should consider this case closed here  as it's better for me to take
the info you gave me and forward what I find to the devs.

Once again, thank you. The resources will be of great use.

Cheers !

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]