From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Yuuki Harano Newsgroups: gmane.emacs.devel Subject: Re: emacs for pure Gtk3 Date: Wed, 29 Apr 2020 16:46:38 +0900 (JST) Organization: Ingage Inc. Message-ID: <20200429.164638.270912316695604169.masm@luna.pink.masm11.me> References: <83o8rd3r8l.fsf@gnu.org> <20200428.224253.781145536690351960.masm@luna.pink.masm11.me> <87k11ykea1.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="80898"; mail-complaints-to="usenet@ciao.gmane.io" Cc: eliz@gnu.org, emacs-devel@gnu.org To: luangruo@yahoo.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Apr 29 09:58:13 2020 Return-path: Envelope-to: ged-emacs-devel@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 1jThbh-000Kxf-QO for ged-emacs-devel@m.gmane-mx.org; Wed, 29 Apr 2020 09:58:13 +0200 Original-Received: from localhost ([::1]:51088 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jThbg-0000We-PW for ged-emacs-devel@m.gmane-mx.org; Wed, 29 Apr 2020 03:58:12 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49800) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jThXO-0006AS-JE for emacs-devel@gnu.org; Wed, 29 Apr 2020 03:57:27 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.90_1) (envelope-from ) id 1jThV3-00039f-Ih for emacs-devel@gnu.org; Wed, 29 Apr 2020 03:53:45 -0400 Original-Received: from shiro.masm11.me ([150.95.182.25]:40080) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jThQb-0000X3-7v; Wed, 29 Apr 2020 03:46:46 -0400 Original-Received: from luna.pink.masm11.me (224.232.12.61.ap.yournet.ne.jp [61.12.232.224]) (using TLSv1.3 with cipher TLS_CHACHA20_POLY1305_SHA256 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by shiro.masm11.me (Postfix) with ESMTPSA id 62577C0147; Wed, 29 Apr 2020 16:46:39 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=masm11.me; s=202002; t=1588146399; bh=g9VUylF5us0mEwBLqgYSSA3DVgv60BOUF6EBVZaxICo=; h=Date:To:Cc:Subject:From:In-Reply-To:References; b=xSK1q1IjJi20crifoBGk8LGYQ8R27sJl2vFD84FPaaKNHt/Za7E6fXdfEikfmFTpF qC6vo597eCmwJ0UtB7w4AfEFdmwxybYR1ewVr+/L6/0GlHK+bcq+JdH6rvjShrldA2 BxTuTQojc0oRT+aJgUOEXneTzqyThSMgYRBilMBM= In-Reply-To: <87k11ykea1.fsf@yahoo.com> X-Mailer: Mew version 6.8 on Emacs 28.0 Received-SPF: pass client-ip=150.95.182.25; envelope-from=masm@masm11.me; helo=shiro.masm11.me X-detected-operating-system: by eggs.gnu.org: First seen = 2020/04/29 03:46:40 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 150.95.182.25 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:248091 Archived-At: On Wed, 29 Apr 2020 14:16:22 +0800, Po Lu wrote: >> I remember that Emacs has previously an issue when multiple display >> environments. I thought that the segfaults was the same issue. >> Was that fixed? > > The multiple display issue is a GTK problem not related to the > segfaults, and is also specific to various GDK backends. AFAICT, GDK's > Wayland backend does not suddenly barf if a connection is abruptly > closed, but the X11 and Broadway backends do. I think I saw such a comment, but I can't find it even in the past code. I seem to have misunderstood. > The segementation faults are something I have personally never > experienced, and I have been running my own fork of your code as a daily > driver for a very long time. Indeed, the segfaults do not occur as far as I tested now. It may be fixed before I knew, or it disappeared... I'll debug if it is reproduced by someone (or me). Thanks. -- Yuuki Harano