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#58956: mark_object, mark_objects(?) crash Date: Thu, 03 Nov 2022 12:27:01 +0200 Message-ID: <83zgd872q2.fsf@gnu.org> References: <874jvi5edp.fsf@melete.silentflame.com> <20221103030046.GA57325@zira.vinc17.org> <83o7to8rh1.fsf@gnu.org> <20221103101308.GD9442@zira.vinc17.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28332"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 58956@debbugs.gnu.org, 1017711@bugs.debian.org, spwhitton@spwhitton.name To: Vincent Lefevre , Andrea Corallo Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Nov 03 11:28:52 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 1oqXSs-000709-5F for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 03 Nov 2022 11:28:50 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oqXS7-000067-BB; Thu, 03 Nov 2022 06:28:03 -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 1oqXS6-00005x-LW for bug-gnu-emacs@gnu.org; Thu, 03 Nov 2022 06:28: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 1oqXS6-0003ku-6d for bug-gnu-emacs@gnu.org; Thu, 03 Nov 2022 06:28:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oqXS5-0002nL-Mi for bug-gnu-emacs@gnu.org; Thu, 03 Nov 2022 06:28:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 03 Nov 2022 10:28: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.166747123910688 (code B ref 58956); Thu, 03 Nov 2022 10:28:01 +0000 Original-Received: (at 58956) by debbugs.gnu.org; 3 Nov 2022 10:27:19 +0000 Original-Received: from localhost ([127.0.0.1]:48103 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oqXRP-0002mK-5P for submit@debbugs.gnu.org; Thu, 03 Nov 2022 06:27:19 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:35674) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oqXRN-0002m5-0Q for 58956@debbugs.gnu.org; Thu, 03 Nov 2022 06:27:17 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oqXRG-0003hL-UM; Thu, 03 Nov 2022 06:27:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=MwMdeKQmyPQYkH9dSeadx2vXVxuUAjAFFYbrJdGg1xQ=; b=m4IJlGZNcKy4 ggn8X1n4ZMfv4+4J21/5QLqAmV8xlczE2APHYFhrpbriFiux2O+hcvSgNX907hP1FG2YhPQ6dxSMv kGCKnYBO041IVaQ73IqHjhyF6W8XHctoECc5YTWsBKSGZTNbVrgVxzclz7zWHysNMi9us93FuK9wW ljG2BZ8kyr84e5mCNNktqPIQ7AVrpfO8wURZp/9y1w4qLwDxZ/1YhZzqsPyj0Eqmw29BTNZ/ptqnC DqNssXNPIhrbeXk0v4oZNnPHgNtZl8OsKOiGlfLlAa9debMvOmhbywtIU4t/RUIb3kidc7S/UshMl d5pAV2q4KTmDv71Ivqx4rQ==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oqXRG-00083F-8N; Thu, 03 Nov 2022 06:27:10 -0400 In-Reply-To: <20221103101308.GD9442@zira.vinc17.org> (message from Vincent Lefevre on Thu, 3 Nov 2022 11:13:08 +0100) 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:246946 Archived-At: > Date: Thu, 3 Nov 2022 11:13:08 +0100 > From: Vincent Lefevre > Cc: spwhitton@spwhitton.name, 58956@debbugs.gnu.org, > 1017711@bugs.debian.org > > 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". Andrea, could you please look into this? The SIGHUP could be because the parent process exits, but that shouldn't cause a crash in the sub-process that performs native compilation? Thanks.