From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Pip Cet Newsgroups: gmane.emacs.devel Subject: Re: [scratch/igc] 985247b6bee crash on Linux, KDE, Wayland Date: Thu, 05 Sep 2024 16:19:29 +0000 Message-ID: <875xrars34.fsf@protonmail.com> References: <8734mezkgo.fsf@gmail.com> <87y1461frv.fsf@gmail.com> <864j6u47g4.fsf@gnu.org> <8634me447j.fsf@gnu.org> <861q1y437s.fsf@gnu.org> <86wmjq2mr2.fsf@gnu.org> 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="4839"; mail-complaints-to="usenet@ciao.gmane.io" Cc: =?utf-8?Q?Gerd_M=C3=B6llmann?= , execvy@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Sep 05 19:41:21 2024 Return-path: Envelope-to: ged-emacs-devel@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 1smGTw-000118-FF for ged-emacs-devel@m.gmane-mx.org; Thu, 05 Sep 2024 19:41:20 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1smGTJ-0004VG-SL; Thu, 05 Sep 2024 13:40:41 -0400 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 1smFCv-0000NN-EI for emacs-devel@gnu.org; Thu, 05 Sep 2024 12:19:41 -0400 Original-Received: from mail-40131.protonmail.ch ([185.70.40.131]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1smFCt-0007GV-PO for emacs-devel@gnu.org; Thu, 05 Sep 2024 12:19:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1725553177; x=1725812377; bh=nB0IIgGphFRkYNXeo3647r6U2U10T+/KDPh5vDSBsc0=; 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; b=j/m/OHs/7oAw+RX4VfBh9isuFfF7GGRXladkkT250AutK1SMXVaeoJ42WF2Z42N6+ QEhos031PUt6SLWrSRGLkByDYG17eAzYxZPpElqz8XWnK3yrfpW2w1zD4JjbSvDpWH ogd4p+nSjmT3xYbFrSU/LjLDmPXdPREOGs7vrkEEw45wSej7AHaAyYdcIjyAN4FzIi WnBGTaeeIQql5fb2Zxumxd/op9R9ViuHKQDxIq5OZnMWcf45AA67aqHUFBQaRlZU/E WzaGUpPZ3DVYwIVNJ+Rv0g8i1UMVYaGtqczV/iWAuqApTXRRXP8n+ddjUynpvZ3qOm yYd0K6ewdd3GQ== In-Reply-To: <86wmjq2mr2.fsf@gnu.org> Feedback-ID: 112775352:user:proton X-Pm-Message-ID: 8d68714e527c219733dbce69d41bd166d5182479 Received-SPF: pass client-ip=185.70.40.131; envelope-from=pipcet@protonmail.com; helo=mail-40131.protonmail.ch X-Spam_score_int: -10 X-Spam_score: -1.1 X-Spam_bar: - X-Spam_report: (-1.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Thu, 05 Sep 2024 13:40:39 -0400 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:323418 Archived-At: "Eli Zaretskii" writes: >> From: Gerd M=C3=B6llmann >> Cc: execvy@gmail.com, pipcet@protonmail.com, emacs-devel@gnu.org >> Date: Thu, 05 Sep 2024 15:57:50 +0200 >> >> Eli Zaretskii writes: >> >> >> That means FRAME_OUTPUT_DATA can be null during the lifetime of a >> >> frame. If that happens, we'll crash exactly in that way in the new co= de >> >> for window frames. >> > >> > We never test for FRAME_OUTPUT_DATA being non-NULL in the code, so I >> > don't think I understand why igc.c is different. >> >> Our scan functions can run at arbitrary times, including when >> FRAME_OUTPUT_DATA is still null. > > OK, but if you look at the backtrace, you will see that in this case > the scan functions were run from within code called by > redisplay_internal, so I very much doubt that FRAME_OUTPUT_DATA was > NULL in this case. But the frame we crashed tracing wasn't the same frame that was being redisplayed. It's possible it was a destroyed ("dead") frame, right? Then frame destruction would have freed and subsequently zeroed its FRAME_OUTPUT_DATA. However, debugging further is the only way to be sure. If the OP still has the core dump + executable for this crash, that should contain the necessary data, even without waiting for the crash to happen again. And it definitely looks like a different bug from the previous reports, which all involved consing up a list in -O3 code using -march=3Dnative. Pip