From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Liam Stitt Newsgroups: gmane.emacs.bugs Subject: bug#44047: current HEAD has been crashing on startup Date: Sun, 1 Nov 2020 06:48:45 -0700 (MST) Message-ID: 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> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40838"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Alpine 2.20 (DEB 67 2015-01-07) Cc: 44047@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Nov 01 14:49:09 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 1kZDjJ-000AWW-3w for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 01 Nov 2020 14:49:09 +0100 Original-Received: from localhost ([::1]:49004 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kZDjI-0006WT-6P for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 01 Nov 2020 08:49:08 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38428) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kZDjC-0006WE-DG for bug-gnu-emacs@gnu.org; Sun, 01 Nov 2020 08:49:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:52698) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kZDjC-0003zz-49 for bug-gnu-emacs@gnu.org; Sun, 01 Nov 2020 08:49:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kZDjC-0002x4-2L for bug-gnu-emacs@gnu.org; Sun, 01 Nov 2020 08:49:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Liam Stitt Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 01 Nov 2020 13:49:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 44047 X-GNU-PR-Package: emacs Original-Received: via spool by 44047-submit@debbugs.gnu.org id=B44047.160423852911328 (code B ref 44047); Sun, 01 Nov 2020 13:49:02 +0000 Original-Received: (at 44047) by debbugs.gnu.org; 1 Nov 2020 13:48:49 +0000 Original-Received: from localhost ([127.0.0.1]:36011 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kZDiz-0002we-9C for submit@debbugs.gnu.org; Sun, 01 Nov 2020 08:48:49 -0500 Original-Received: from arnold.cuug.ab.ca ([67.231.23.5]:42694) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kZDix-0002wU-6W for 44047@debbugs.gnu.org; Sun, 01 Nov 2020 08:48:47 -0500 Original-Received: by arnold.cuug.ab.ca (Postfix, from userid 10022) id BC59BE0371; Sun, 1 Nov 2020 06:48:45 -0700 (MST) Original-Received: from localhost (localhost [127.0.0.1]) by arnold.cuug.ab.ca (Postfix) with ESMTP id B4007E033C; Sun, 1 Nov 2020 06:48:45 -0700 (MST) In-Reply-To: <83h7qhf2c8.fsf@gnu.org> 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:192373 Archived-At: On Mon, 26 Oct 2020, Eli Zaretskii wrote: > 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. -- Liam Stitt stittl@cuug.ab.ca