From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Vincent Lefevre Newsgroups: gmane.emacs.bugs Subject: bug#58956: mark_object, mark_objects(?) crash Date: Thu, 3 Nov 2022 11:13:08 +0100 Message-ID: <20221103101308.GD9442@zira.vinc17.org> References: <874jvi5edp.fsf@melete.silentflame.com> <20221103030046.GA57325@zira.vinc17.org> <83o7to8rh1.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35278"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.2.7+51 (a318ca5a) vl-149028 (2022-10-21) Cc: 58956@debbugs.gnu.org, 1017711@bugs.debian.org, spwhitton@spwhitton.name To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Nov 03 11:14:18 2022 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 1oqXEo-0008zk-S3 for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 03 Nov 2022 11:14:18 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oqXEc-0002s8-2m; Thu, 03 Nov 2022 06:14:06 -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 1oqXEY-0002pu-Hj for bug-gnu-emacs@gnu.org; Thu, 03 Nov 2022 06:14:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oqXEY-0001Xu-39 for bug-gnu-emacs@gnu.org; Thu, 03 Nov 2022 06:14:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oqXEX-0002Iv-MW for bug-gnu-emacs@gnu.org; Thu, 03 Nov 2022 06:14:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Vincent Lefevre Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 03 Nov 2022 10:14:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 58956 X-GNU-PR-Package: emacs Original-Received: via spool by 58956-submit@debbugs.gnu.org id=B58956.16674703928789 (code B ref 58956); Thu, 03 Nov 2022 10:14:01 +0000 Original-Received: (at 58956) by debbugs.gnu.org; 3 Nov 2022 10:13:12 +0000 Original-Received: from localhost ([127.0.0.1]:48088 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oqXDk-0002Hh-5E for submit@debbugs.gnu.org; Thu, 03 Nov 2022 06:13:12 -0400 Original-Received: from joooj.vinc17.net ([155.133.131.76]:33692) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oqXDj-0002HZ-41 for 58956@debbugs.gnu.org; Thu, 03 Nov 2022 06:13:11 -0400 Original-Received: from smtp-zira.vinc17.net (128.119.75.86.rev.sfr.net [86.75.119.128]) by joooj.vinc17.net (Postfix) with ESMTPSA id 257C9BD; Thu, 3 Nov 2022 11:13:09 +0100 (CET) Original-Received: by zira.vinc17.org (Postfix, from userid 1000) id E7C5D2800212; Thu, 3 Nov 2022 11:13:08 +0100 (CET) Content-Disposition: inline In-Reply-To: <83o7to8rh1.fsf@gnu.org> X-Mailer-Info: https://www.vinc17.net/mutt/ 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: , Original-Sender: "bug-gnu-emacs" Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:246945 Archived-At: On 2022-11-03 08:47:06 +0200, Eli Zaretskii wrote: > > On 2022-11-02 14:24:51 +0200, Eli Zaretskii wrote: > > > Signal 1 is SIGHUP, AFAIU. Why should Emacs receive SIGHUP in the > > > middle of GC, I have no idea. Maybe ask the user what was he doing at > > > that time. E.g., could that be a remote Emacs session? > > > > No, it is on my local machine. > > So how come Emacs gets a SIGHUP? This is the crucial detail that is > missing here. Basically, if SIGHUP is delivered to Emacs, Emacs is > supposed to die a violent death. I suspect the SIGHUP comes from Emacs itself. According to strace output, the only processes started by Emacs are "/usr/bin/emacs" (there are many of them). I don't see what other process could be aware of the situation. Unfortunately, I couldn't reproduce the issue with strace (I suspect some race condition). > > I run emacs, and quit it immediately. The generation of the core dump > > is almost 100% reproducible. Ditto with "emacs -nw". > > Wait, you mean the crash is during exiting Emacs? For this test, yes. In general, I don't know. > That could mean Emacs receives some input event when it's half-way > through the shutdown process, and the input descriptor is already > closed. Note that the process that crashes is not the Emacs I started, but a subprocess run by Emacs itself, since it has arguments like "-no-comp-spawn --batch -l /tmp/emacs-async-comp-url.el-FGov4z.el". However, it also happened that the Emacs I started immediately crashed (this occurred only once, though). -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)