From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#44047: current HEAD has been crashing on startup Date: Sun, 01 Nov 2020 17:34:43 +0200 Message-ID: <83o8khf5v0.fsf@gnu.org> References: <83v9f8srih.fsf@gnu.org> <83wnzmpa5d.fsf@gnu.org> <835z76p2hp.fsf@gnu.org> <83a6wgoq4j.fsf@gnu.org> <83k0vjmurb.fsf@gnu.org> <83h7qhf2c8.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14357"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 44047-done@debbugs.gnu.org To: Liam Stitt Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Nov 01 16:36:12 2020 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 1kZFOt-0003er-DN for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 01 Nov 2020 16:36:11 +0100 Original-Received: from localhost ([::1]:33208 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kZFOs-0001TY-4P for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 01 Nov 2020 10:36:10 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60764) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kZFOk-0001Sj-O5 for bug-gnu-emacs@gnu.org; Sun, 01 Nov 2020 10:36:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:54940) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kZFOk-0000E9-EI for bug-gnu-emacs@gnu.org; Sun, 01 Nov 2020 10:36:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kZFOk-0008Qx-Bt for bug-gnu-emacs@gnu.org; Sun, 01 Nov 2020 10:36:02 -0500 Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-To: bug-gnu-emacs@gnu.org Resent-Date: Sun, 01 Nov 2020 15:36:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: cc-closed 44047 X-GNU-PR-Package: emacs Mail-Followup-To: 44047@debbugs.gnu.org, eliz@gnu.org, stittl@cuug.ab.ca Original-Received: via spool by 44047-done@debbugs.gnu.org id=D44047.160424490332343 (code D ref 44047); Sun, 01 Nov 2020 15:36:02 +0000 Original-Received: (at 44047-done) by debbugs.gnu.org; 1 Nov 2020 15:35:03 +0000 Original-Received: from localhost ([127.0.0.1]:38252 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kZFNn-0008Pb-2Q for submit@debbugs.gnu.org; Sun, 01 Nov 2020 10:35:03 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:60500) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kZFNl-0008P4-4D for 44047-done@debbugs.gnu.org; Sun, 01 Nov 2020 10:35:01 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:56327) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kZFNf-0008QF-Ih; Sun, 01 Nov 2020 10:34:55 -0500 Original-Received: from [176.228.60.248] (port=3568 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kZFNf-0002PF-1U; Sun, 01 Nov 2020 10:34:55 -0500 In-Reply-To: (message from Liam Stitt on Sun, 1 Nov 2020 06:48:45 -0700 (MST)) 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:192405 Archived-At: > Date: Sun, 1 Nov 2020 06:48:45 -0700 (MST) > From: Liam Stitt > cc: 44047@debbugs.gnu.org > > > Ping! Any news on this? > > Belatedly, yes: the problem spontaneously went away(!), after I > accidentally full-screened my terminal emulator then restored it to > normal size. While I am by no means certain of why that should have > such an effect, what digging I have been able to do suggests the > explanation might involve (1) a SIGWINCH that operation generated which > (2) caused that particular screen-sessions's bash to set $COLUMNS and > $LINES, which were previously nonextant. > > I haven't been able to replicate the crash since. I can only suggest > closing this bug report for now, and I'll reopen it if I manage to > figure out how to trigger the crash again. OK, thanks. Done.