From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id E878415813A for ; Sat, 11 Jan 2025 16:31:25 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B21BEE081A; Sat, 11 Jan 2025 16:31:19 +0000 (UTC) Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com [IPv6:2a00:1450:4864:20::635]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 6DA2DE07F2 for ; Sat, 11 Jan 2025 16:31:18 +0000 (UTC) Received: by mail-ej1-x635.google.com with SMTP id a640c23a62f3a-aa68b513abcso526316966b.0 for ; Sat, 11 Jan 2025 08:31:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1736613076; x=1737217876; darn=lists.gentoo.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=Ynbvu3koTYffY+XxAQOsSi1PFYEpk8vE86l4+3Qjw30=; b=cIn9a8LX5QoMvZBN/OWGY4vcqpU/PvWZJjW312LhIDHIOXK9KaTrUDRIgvs1PPyhPc Bjm9uzm4SOJPx9yEgf5bbmgn+q0MxUHIZ6wKxmKFMB/S+xFiEI6wvj9F4KMrEvJcnAWH S3bc0ju3UnaADhxi5KSvaxJcBu11exq1eD1Tnep3QYTD0G37UapOvfn6Sj27LdSUY7EA t0SfGLHBTVrC/rMetCBlyz6Q++CVdQaFXjR+VubNHGBfwQb5xfx40BtOaX5VfGDAJrVI qsFufkF8NfGONcY5PNeGEgZKJr2INBobrgOZDraJXqgjZKif2lfTvaz49Rd6yf4FWnvc dvjg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736613076; x=1737217876; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=Ynbvu3koTYffY+XxAQOsSi1PFYEpk8vE86l4+3Qjw30=; b=gL1nvdSme/103UK3jLwsZP+E8gx8h6pU1lFwQ5DmOipG1tBJTCtlSfAdHGVET0lzjt pV3ZYu9uH4zw9b8RfW6Zby9r5f5uxgaAPBR1gOljS+vHm6SHXUiux4AC/ZQOe5a/af74 Bcdr5EMR7RiX7G8Hu6yf6OKNM5DpSgDnB6kPYx2ixwJDBTCEWWiea/5XQa5M/PEuISm0 ++8pkI8E/AR5YgWcdxhLFFeY0HFK8eYYR6pt849a1+URA7Qt47K7nD7MTW9Q5QX8WYjh fACRgSET+22zB1Qfri4rWuF0Vh4fmGeLTGvjvOwr/BJXMkJADZSiSoJ2bRi9sXgKJvcr AXmg== X-Gm-Message-State: AOJu0YzV/EiDLqBkHUH4JZ4azGk68VQibq+kepcixjSUtNMnkblZ6NxP F4iNttc4P6zK9jGZ7I0D4pkKyC9q6gz8VsGU48dCe3BJ6llynzFs8oXarc5s X-Gm-Gg: ASbGncsSevYfL6g2nj6g/vyPDkbnRhKeB5mPZkad3dAmXOUaN7BDBVuqrHJmTyS0YCO apPyCKhy8Vw/mCEc224A+qny3J6MJ3U45Cx6JmQyuBoT1AZlLvEhfEr6Bi7E2vH4PjST21XH3p4 qCIeZV2nQgf9xNfG++kwU+kTcoOhRMGRKmFvlN7FNvvprXFvpOgKPO1dIxHG5NqVm1FwMJe6pOe u/8++pQNnGP8G/AUjUD9bYZUaL/f83lMbAU3lJ7tCuB16VEP6GS9uobcD2DfVMGG9QyvWvcMENE hhF6SLlcfIMc+A== X-Google-Smtp-Source: AGHT+IGNy7JHK7Lmn2UU7GhSnYPVEOsm8QyyhjofjaEBcs9H+R3zpGtD7JBm8Xo2U4k2DSHPZDaJOQ== X-Received: by 2002:a17:907:3a96:b0:ab2:b5f1:568c with SMTP id a640c23a62f3a-ab2b5f15bf1mr861082866b.28.1736613076344; Sat, 11 Jan 2025 08:31:16 -0800 (PST) Received: from tux (178-223-139-140.dynamic.isp.telekom.rs. [178.223.139.140]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-ab2c905ec28sm288876366b.16.2025.01.11.08.31.15 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 11 Jan 2025 08:31:15 -0800 (PST) Date: Sat, 11 Jan 2025 17:31:14 +0100 From: Filip =?utf-8?Q?Milosavljevi=C4=87?= To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] Re: Subject: Digest of gentoo-user@lists.gentoo.org issue 4066 (205256-205258) Message-ID: References: <20250111143208.12247E0814@pigeon.gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="fogfmtqxvb66ptn7" Content-Disposition: inline In-Reply-To: <20250111143208.12247E0814@pigeon.gentoo.org> X-Archives-Salt: 8b6d2ef4-b633-4e0f-b7bc-df2f37a2ef97 X-Archives-Hash: f171474d56fd760c66e0e71a1d1b4373 --fogfmtqxvb66ptn7 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 e= rror) > 205256 - Filip Milosavljevi=C4=87 > >[gentoo-user] 'mbsync -a' terminated by signal SIGSEGV (Address boundary e= rror) > 205257 - Michael > >[gentoo-user] update catch-22 with Wifi > 205258 - Frank Steinmetzger > >Date: Mon, 6 Jan 2025 11:52:18 +0100 >From: Filip Milosavljevi=C4=87 >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=C4=87 >Date: Mon, 06 Jan 2025 11:54:10 +0000 >From: Michael >To: gentoo-user@lists.gentoo.org >Subject: Re: [gentoo-user] 'mbsync -a' terminated by signal SIGSEGV (Addre= ss > boundary error) > >On Monday 6 January 2025 10:52:18 Greenwich Mean Time Filip Milosavljevi= =C4=87 >wrote: >> Greetings everyone, glad to finally be part of the club. > >Welcome! :-) > > Thank you !=20 >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 gli= bc, >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 wel= l. Only thing I have to add are : 1. The Gentoo Wiki is exceptionaly well written, some that's not in IT=20 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=C4=87 --fogfmtqxvb66ptn7 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQTwSPWAdW5ckbIApEXPAgzb27WhaQUCZ4Kc0AAKCRDPAgzb27Wh ac2qAP4qxpfc9BZImMe34/6jJ6y64xO7t5UwNtpoAoD3DB2ZMgEA8meCtm8JkCbT 8zb9WbVBp7TAMSmhzeX4gAkTV7ugXwE= =FQ9D -----END PGP SIGNATURE----- --fogfmtqxvb66ptn7--