From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Daniel Clemente Newsgroups: gmane.emacs.bugs Subject: bug#71177: 30.0.50; crash when opening and closing many TTY frames in succession Date: Sat, 25 May 2024 11:04:39 +0000 Message-ID: References: <86o78v0zx6.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000a7330506194541d1" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1046"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 71177@debbugs.gnu.org, Eli Zaretskii To: Po Lu Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat May 25 13:07:20 2024 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 1sApFA-000Adf-6g for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 25 May 2024 13:07:20 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sApEp-0007nq-CC; Sat, 25 May 2024 07:06:59 -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 1sApEm-0007nQ-Db for bug-gnu-emacs@gnu.org; Sat, 25 May 2024 07:06:57 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1sApEl-00061d-Op for bug-gnu-emacs@gnu.org; Sat, 25 May 2024 07:06:56 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1sApEt-0004TK-0Y for bug-gnu-emacs@gnu.org; Sat, 25 May 2024 07:07:03 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Daniel Clemente Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 25 May 2024 11:07:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 71177 X-GNU-PR-Package: emacs Original-Received: via spool by 71177-submit@debbugs.gnu.org id=B71177.171663518017172 (code B ref 71177); Sat, 25 May 2024 11:07:02 +0000 Original-Received: (at 71177) by debbugs.gnu.org; 25 May 2024 11:06:20 +0000 Original-Received: from localhost ([127.0.0.1]:42804 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sApEC-0004Su-Fb for submit@debbugs.gnu.org; Sat, 25 May 2024 07:06:20 -0400 Original-Received: from mail-yw1-f180.google.com ([209.85.128.180]:50590) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sApEA-0004Sm-6L for 71177@debbugs.gnu.org; Sat, 25 May 2024 07:06:18 -0400 Original-Received: by mail-yw1-f180.google.com with SMTP id 00721157ae682-62a2424ed00so801437b3.1 for <71177@debbugs.gnu.org>; Sat, 25 May 2024 04:06:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1716635105; x=1717239905; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=u+7THA8NoWtV2G8QuCtTbLaz6c5HVXOcWQ1U7rHqoQs=; b=V///8FTNKEtOlk/Mg0KwnXFFYwQ9ZKBWZaQV+p+68IOtKhcoQLveOph1gaTU7xcQAB CD5YcoQbENVRQ1hzDxKsatvosdfhpS1GuOODlM51XioBFbJ2OGu15xPUx6TxRQujYD6t fYy7m2nQBpbmlQCicDTMNv6kAL9yOZgt+vqcs/P5X6xljfOXRec+VhOa2EPTMuWxWdLr EBZcgwjIhGv7wBB6JCdI1yJhDQws/plg4CTxD73CmUwkKh8PyNSBWfZ4HESfIwg4Mwh+ TmFoia4MJon1YKfENDjdJTh01zSX9KG89y/A0qFToP4tvtlj862poADm8XaCvFDUfdGw aggQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716635105; x=1717239905; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=u+7THA8NoWtV2G8QuCtTbLaz6c5HVXOcWQ1U7rHqoQs=; b=RPp37Pkr/nijf/hhm2zFYU28MDeZ/jg6AKL4VyH20eO0oZrQGoVAxeA1SoQd3BIunl eRFclPUNFlBjz3QxloJvKd6eBktM6qNMKCnWH5up43HCaRnN8A7cMJ2IIxoLDFVKS8hI KDbQLkWVPVL+2825G/PGdVrM6OsOajFXvFFoliUGW70NZAbiy1O3OpqUcFa+NS6FpAgr gtbdmmzke/mWflzfXu20/ts1oXxOMMSkBI8t/kI57HSQBRCC9paOsotlKDIIwEE6WtFo bU5NHQpruDnHbQyIQsg13WrM2xiEg2jWJ7mWZCiTGlpnDQzo3KEJhdeUc52Y78JzrQ4f CXNw== X-Forwarded-Encrypted: i=1; AJvYcCUl3r7lGMWO6vNMmDCtyFKGP4D0ZcLu+U8UqGrXCt4jbMA50QdemgDex+ajw2D2Wj7FA+VPPXGKawGE2QqxP5ZueXVj11s= X-Gm-Message-State: AOJu0YzY+qJeVI9g2HC8zqaGiT2q5IL3qOeWxmF/DBSTYJPi3Ypy7OK1 7cTAV1oPc9GqwiY7gn5Icb/JXlervTwXCMF+U37k4+zAyI9+hP1sgHheG0zH7xolDZeLPMmDufY ESuKxtao217+gJm7XfnXshRNtfOo= X-Google-Smtp-Source: AGHT+IE4jrvci2X/6sNwB1S9Xmkp11twkveBmPpUVTcteGNBqKFAoo6ET4GHpVKNaLBmAi2qDeTvlFHQD+F2hHx9UOs= X-Received: by 2002:a0d:eb54:0:b0:61a:bc15:8359 with SMTP id 00721157ae682-62a08d29241mr45944877b3.9.1716635105175; Sat, 25 May 2024 04:05:05 -0700 (PDT) In-Reply-To: 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:285857 Archived-At: --000000000000a7330506194541d1 Content-Type: text/plain; charset="UTF-8" > That's a red herring. It's because Daniel is running Emacs under GDB > that his backtrace ends with a SIGPIPE, while the backtrace for the > crash lies elsewhere. True, this was a SIGPIPE (still not a crash), and gdb was stopping here. By running "cont" I could make it continue. After running "handle SIGPIPE noprint pass", and continuing the same behaviour for ~30 seconds, I saw the real crash (SIGSEGV). The cause of the crash is the other bug I reported, bug#71176 (tty-set-up-initial-frame-faces, face_at_buffer_position, default_face = 0x0), so I posted the new backtrace there. So in here we just discovered that opening+closing frames is a way to reproduce bug#71176, but I think the bug is 71176 and this one can be closed. > It might help if you post the details of how you "launch a new > emacsclient with a keypress and kill it with another keypress". IOW, > please describe the recipe to reproduce the problem starting from > "emacs -Q -nw --daemon". I found a simpler formula, by launching and killing emasclient in a bash loop. Details at bug#71176. On Sat, 25 May 2024 at 00:37, Po Lu wrote: > Eli Zaretskii writes: > > > I think it crashes because of this SIGPIPE. I hope some Unix expert > > will be able to explain why Emacs gets get SIGPIPE in this scenario. > > Perhaps because you kill emacsclient too quickly? > > That's a red herring. It's because Daniel is running Emacs under GDB > that his backtrace ends with a SIGPIPE, while the backtrace for the > crash lies elsewhere. > > (gdb) handle SIGPIPE noprint pass > > is probably in order, I suspect. > --000000000000a7330506194541d1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> That's a red herring.=C2=A0 It&= #39;s because Daniel is running Emacs under GDB
> that his backtrace ends with a SIGPIPE, while the backtrace for the > crash lies elsewhere.

True, this was a SIGPIPE (still not a crash), and= gdb was stopping here. By running "cont" I could make it continu= e.
After running "handle SIGPIPE noprint pass", and con= tinuing the same behaviour for ~30 seconds, I saw the real crash (SIGSEGV)= .

The cause of the crash is the other bug I report= ed, bug#71176 (tty-set-up-initial-frame-faces, face_at_buffer_position, def= ault_face =3D 0x0), so I posted the new backtrace there.

=
So in here we just discovered that opening+closing frames is a w= ay to reproduce bug#71176, but I think the bug is 71176 and this one can be= closed.


> It might help if = you post the details of how you "launch a new
> emacsclient with= a keypress and kill it with another keypress".=C2=A0 IOW,
> please describe the recipe to reproduce the problem starting from
> "emacs -Q -nw --daemon".

I found a = simpler formula, by launching and killing emasclient in a bash loop. Detail= s at bug#71176.



On Sat, 25 May 2024 at 00:37, Po Lu= <luangruo@yahoo= .com> wrote:
Eli Zaretskii <eli= z@gnu.org> writes:

> I think it crashes because of this SIGPIPE.=C2=A0 I hope some Unix exp= ert
> will be able to explain why Emacs gets get SIGPIPE in this scenario. > Perhaps because you kill emacsclient too quickly?

That's a red herring.=C2=A0 It's because Daniel is running Emacs un= der GDB
that his backtrace ends with a SIGPIPE, while the backtrace for the
crash lies elsewhere.

=C2=A0 (gdb) handle SIGPIPE noprint pass

is probably in order, I suspect.
--000000000000a7330506194541d1--