From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs Date: Tue, 30 Mar 2021 17:05:14 +0200 Message-ID: <9f6993e1-642b-75f9-1820-f7521d047943@gmx.at> References: <87im5ofp3z.fsf@md5i.com> <83czvvdw7o.fsf@gnu.org> <14e14f28-7ece-cd98-5e49-d4583a0153a0@gmx.at> <16b279ef-a1c2-cd41-b18c-69383174c72a@gmx.at> <87a6qs7z60.fsf@md5i.com> <83eeg3kawg.fsf@gnu.org> <83y2e6kp9t.fsf@gnu.org> <83tuouknpb.fsf@gnu.org> <83sg4eknh5.fsf@gnu.org> <83r1jykmt0.fsf@gnu.org> <2d0dbdc8-3678-cd21-234a-9c63bb004629@gmx.at> <83h7ksk89q.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39354"; mail-complaints-to="usenet@ciao.gmane.io" Cc: mwd@md5i.com, schwab@linux-m68k.org, 47244@debbugs.gnu.org, mwd@cert.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Mar 30 17:06:11 2021 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 1lRFwZ-000A64-Oh for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 30 Mar 2021 17:06:11 +0200 Original-Received: from localhost ([::1]:50938 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lRFwY-0002RH-LT for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 30 Mar 2021 11:06:10 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49566) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lRFwQ-0002Qd-Kk for bug-gnu-emacs@gnu.org; Tue, 30 Mar 2021 11:06:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:41075) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lRFwQ-0004UR-Cb for bug-gnu-emacs@gnu.org; Tue, 30 Mar 2021 11:06:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lRFwQ-0004Tn-7P for bug-gnu-emacs@gnu.org; Tue, 30 Mar 2021 11:06:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 30 Mar 2021 15:06:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 47244 X-GNU-PR-Package: emacs Original-Received: via spool by 47244-submit@debbugs.gnu.org id=B47244.161711673017145 (code B ref 47244); Tue, 30 Mar 2021 15:06:02 +0000 Original-Received: (at 47244) by debbugs.gnu.org; 30 Mar 2021 15:05:30 +0000 Original-Received: from localhost ([127.0.0.1]:52617 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lRFvt-0004ST-Oy for submit@debbugs.gnu.org; Tue, 30 Mar 2021 11:05:29 -0400 Original-Received: from mout.gmx.net ([212.227.15.15]:42601) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lRFvs-0004SD-3I for 47244@debbugs.gnu.org; Tue, 30 Mar 2021 11:05:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1617116716; bh=PJuyIzbD7i6lRaO6Co1lMRI4f41JIPqJZKPw6NoPaa0=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=HRmp512FtEE2TSlxbTYueb4DZFwopUD1grhf31rpeWBvHTcgoy4g+YvxqiWP52x2a 0LZJpSIJOh8hIlljaWGvevSz7rqB/CZIT6twCzn1NRnv8/eAec4YjpbMsf+N1NMuIZ 2ppP2yrpDTRwAqol1EcFaALfL4oOUNSLVR2C9xRY= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from [192.168.1.100] ([212.95.5.203]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MatRZ-1m1xOJ17tb-00cPq1; Tue, 30 Mar 2021 17:05:16 +0200 In-Reply-To: <83h7ksk89q.fsf@gnu.org> Content-Language: en-US X-Provags-ID: V03:K1:SaUPCF3ZghTlVhCiRzXgA4uv4NMb550pu06bgrAXslPqYyvB6L7 MZG4ys/kDG7Zw89j/Ut1Bp1Nh2n8uIu1CkCDy4+hv6Rf7CHFqvwXc5Et8dPSWBolnTmXbm+ MNoMRW0b0T9qJd3cTiNS27jkJh/Zm0FjEiUsNSvIF/DgPqaAod+sVsQiexR31UqQ1ml+mO2 lCubFdX2i/mh3nUAoc1wg== X-UI-Out-Filterresults: notjunk:1;V03:K0:wXrU/yLMLy0=:dPovdslyZcKdqXUzFj60Wf EB9/kvo8ZhOYr0qPAXzjjoK9mKxT0L8HBGCQJ8L6KIy9qQFNM4quDcrogAgKpE6sdXh6P/DYr WlxY5m8+KkYTjvbcaLiUHVcnO32u+t7Jcepsgs8XsRUO6Jr0gC4V6dy8sQG95UTauc/GGmxfR e03JDqHcewHb0EhLJwbJMthT0tT20iKQKOTc+H2XCZ6b7cgT28XO/xH8o7KIrHw3WWSVxK9lx nxZbIJJ4hbu5sqQRu0vGn99Gg3QIBzu4rp0HlP8Ucj8ZE6BVbHaysvfeysgSf+Ivun+2/NtQM bJui2lID3FpD0D2Xs0HZbPWQRB8vc2QYItxIuT+c4xaOHNEaxeYwMsK5vZyr3XU8Ni0b2C195 BJRvg6Ik2sQFDZH6hBHIeuwSx7bkMBP9jtaW+RcMrhfc7uMc8oK7A93R1VuIAtfGafcWgjEno akIWcrzhYmY02pp0xsTvXJMk0kRJnwDYyXR+JdmmcTD5XeDkY00OHq3jgVwDhoOR5Xf1BIEkz bCDGel4dc/2q8Fhgm2GlGZ1ZCHbeAxUh0Eqbm+xK8jmMonwSEOkFivA6se7dJaAKPDdkfg+uV 2k9b1kxJLEyMRXd7OiecmoFjlrDo2dH9dSMCD/9ztg8PQ567VUWHef/P+LoEO00HA0YbQsB5m XIR+2XpRCBcicHfhdRY3Q2dFdUQ7ktMfmBEJM69XalobeFhdYb+QSLg4sAt+7DK5PMTkCgfXL Zr7yRSr0MtRRB+gCADuuaxTGbp6Tsc50Dj3A55mpNNLSZ027xkqnpSgNr+TKXKF7X0HnVJoG 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" Xref: news.gmane.io gmane.emacs.bugs:203311 Archived-At: > Maybe instead of trying to find the exact culprit, we should simply > protect this code: > > /* Make sure the current window's buffer is selected. */ > set_buffer_internal (XBUFFER (XWINDOW (selected_window)->contents)); > > from selecting a dead buffer? For example, by using > other_buffer_safely if the selected-window's buffer is dead. The problem is that we already detect this situation too late in order to tell who the real culprit is. For example, a dead buffer stored in the selected_window's contents field could have been a dead current_buffer before. So for some time we could have been already running with a dead buffer in that filed. Long enough maybe to cause havoc elsewhere. And what happened in between might not have used set_buffer_internal but accessed that buffer more directly. martin