From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Pip Cet via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#75209: 30.0.93; Emacs reader failed to read data in "/home/nlj/.cache/org-persist/gc-lock.eld" Date: Wed, 01 Jan 2025 21:09:24 +0000 Message-ID: <87zfkakzsp.fsf@protonmail.com> References: <878qrxgg74.fsf@Phoenix> <864j2lnf1j.fsf@gnu.org> <87zfkddk1l.fsf@Phoenix> <86zfkdlz39.fsf@gnu.org> <87a5camnyu.fsf@protonmail.com> <86r05ml63w.fsf@gnu.org> Reply-To: Pip Cet Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16480"; mail-complaints-to="usenet@ciao.gmane.io" Cc: yantar92@posteo.net, 75209@debbugs.gnu.org, njackson@posteo.net To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Jan 01 22:10:19 2025 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1tT5yt-00049r-7t for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 01 Jan 2025 22:10:19 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tT5yf-0006dZ-09; Wed, 01 Jan 2025 16:10:05 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tT5yd-0006b3-HJ for bug-gnu-emacs@gnu.org; Wed, 01 Jan 2025 16:10:03 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1tT5yd-0007jD-8G for bug-gnu-emacs@gnu.org; Wed, 01 Jan 2025 16:10:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debbugs.gnu.org; s=debbugs-gnu-org; h=MIME-Version:References:In-Reply-To:From:Date:To:Subject; bh=CCOjE1/d3CIZ3EHuYxj4FObyoxRV2OwSvngXpeH7OWI=; b=peAuQulWx8CKP6M1UpaOMoBiJfOvUbGO0UUZ1P3fLhc93IfAfGVDeSoWA3zS6cHoBuKGBy4d3ai3ckrC8Qz/GRB5nKqROHCaMRy04DXzgajDVdl2HAdfcyKtTkRUI8YEe1adY5xiIe7fvmImmXy6la3xIz5b4EfhMo+6QBAWYkAePbozPV6dttwwW36lg5THZ3vY9ji+6VZu/H1lnQDAvWJB52v7RrjK3L7I0MCUE1wlkmW2v6KS42+doxvGxrXfHdmAn0KnucXQQTr3PoWtyC8lV2fFNpOv6AtXmFo4OJ6uiXdSto3YrtYmRfJG51zSGldAKfRPjVdz1sEti+TO2w==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1tT5yc-0005Us-PZ for bug-gnu-emacs@gnu.org; Wed, 01 Jan 2025 16:10:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Pip Cet Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 01 Jan 2025 21:10:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 75209 X-GNU-PR-Package: emacs Original-Received: via spool by 75209-submit@debbugs.gnu.org id=B75209.173576577821080 (code B ref 75209); Wed, 01 Jan 2025 21:10:02 +0000 Original-Received: (at 75209) by debbugs.gnu.org; 1 Jan 2025 21:09:38 +0000 Original-Received: from localhost ([127.0.0.1]:40651 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tT5yD-0005Tv-Vu for submit@debbugs.gnu.org; Wed, 01 Jan 2025 16:09:38 -0500 Original-Received: from mail-4322.protonmail.ch ([185.70.43.22]:48385) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1tT5yA-0005Th-Te for 75209@debbugs.gnu.org; Wed, 01 Jan 2025 16:09:36 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1735765768; x=1736024968; bh=CCOjE1/d3CIZ3EHuYxj4FObyoxRV2OwSvngXpeH7OWI=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=qfPBojjvq6uSskNrq52eNqe38g3BBSVARUSVOEHricjtUVc3lCQ9NjbNT10cORSVX pLaYQXMtSW8S6AG1pEJB9vozgDD959rYNb0UH/A772IwCeSgXvFCEA1F502YtWNUbk ojvli1PP4Tsz+iKJsOYxFDeVsPJPtkX+jdaxhelJdpOfwaejrjZUuKVRovb31Lcg7d MS0LErRY2zfwGqmOhrEkH5V4aOieqVHblKDTudZXjov8c0gWejeOiNYqkPOQ6VKA0b mDXa825T0jzSAIpN4fd19GE6OTQooCKSQHG2veWVmIrwQ7j/vLcXnOYNrCA6ksDy1U hq9p1jl9ED3Tg== In-Reply-To: <86r05ml63w.fsf@gnu.org> Feedback-ID: 112775352:user:proton X-Pm-Message-ID: 20ae6e07730b9c1bc74b7f18227047e08a6bd90f X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:298073 Archived-At: "Eli Zaretskii" writes: >> Date: Wed, 01 Jan 2025 17:41:57 +0000 >> From: Pip Cet >> Cc: "N. Jackson" , yantar92@posteo.net, 75209@debbu= gs.gnu.org >> >> I'm assuming that the resolution was that the file was read before we >> finished writing it. I've run into the same issue a number of times >> (interrupting and resuming Emacs builds leads to build failures, "make >> bootstrap" makes them go away). >> >> Can we consider modifying the .elc format to have a footer indicating >> that the file is complete? > > The .elc file is supposed to be created only when the compilation is > complete and successful. If you look at byte-compile-file, you will You're right. Sorry for the noise. The most likely explanation is I missed a "Pure Lisp storage overflowed" message which "explained" it, because I just tried and that's what happened. There's a bug in pin_string which assumes no purespace overflow, and corrupts bytecode after one, so it's entirely possible that an .elc file was truncated. Probably not worth fixing at this point. I'll try interrupting a few more builds when no-purespace is merged. Pip