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#60144: 30.0.50; PGTK Emacs crashes after signal Date: Sun, 18 Dec 2022 13:43:03 +0200 Message-ID: <83fsddey48.fsf@gnu.org> References: <87edsxfop0.fsf@yahoo.com> <83359dgt7v.fsf@gnu.org> <87a63lfcz7.fsf@yahoo.com> <83y1r5f6lh.fsf@gnu.org> <875ye9f385.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5887"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 60144@debbugs.gnu.org, karl@karlotness.com To: Po Lu Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Dec 18 12:44:11 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 1p6s5P-00018Y-Mw for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 18 Dec 2022 12:44:07 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p6s5L-00017V-OG; Sun, 18 Dec 2022 06:44:03 -0500 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 1p6s5K-00017H-NA for bug-gnu-emacs@gnu.org; Sun, 18 Dec 2022 06:44:02 -0500 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 1p6s5K-0007t7-BS for bug-gnu-emacs@gnu.org; Sun, 18 Dec 2022 06:44:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1p6s5K-0007wT-44 for bug-gnu-emacs@gnu.org; Sun, 18 Dec 2022 06:44:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 18 Dec 2022 11:44:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 60144 X-GNU-PR-Package: emacs Original-Received: via spool by 60144-submit@debbugs.gnu.org id=B60144.167136378230500 (code B ref 60144); Sun, 18 Dec 2022 11:44:02 +0000 Original-Received: (at 60144) by debbugs.gnu.org; 18 Dec 2022 11:43:02 +0000 Original-Received: from localhost ([127.0.0.1]:33460 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1p6s4M-0007vs-Ga for submit@debbugs.gnu.org; Sun, 18 Dec 2022 06:43:02 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:43956) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1p6s4L-0007vV-Cg for 60144@debbugs.gnu.org; Sun, 18 Dec 2022 06:43:01 -0500 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 1p6s4F-0007qh-N7; Sun, 18 Dec 2022 06:42:55 -0500 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=hDqQO7L9OdYpHCcHm49YPvBs+s5QVU6JsUheaS7owDo=; b=I4nFf3AYBClO 7x/ontpDkDPi8pgasnfzRth0Wy0Xmu0Ky4+YpraExE6LCu+Q1WZytXdl7d8HdQ5hoUUxdtyOtoigG vpMjG+lYaAOnrh3QOpgvb+kdCU3SiMKn1tfbwXEYRG3mfMD1VAWrZSQJwHWT+gX6M/5tQAMlJqB7S JNXQ3BsxBdQSXnfbkVt+/+OYD4d7QPpQCHsRuUeTbrQFin7ArZFtT68JMfZdPmueSl/+ZOzYqmI0l E/EVwr8Qkku5LD7/uKFQF+6UZTkI/mWlBxycNS8a4XaPwmsw15xN0GlWGRd24JAAClHhUOnSdifVh WP7N504jRFVgf68A8JfbrQ==; 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 1p6s4F-0006y8-82; Sun, 18 Dec 2022 06:42:55 -0500 In-Reply-To: <875ye9f385.fsf@yahoo.com> (message from Po Lu on Sun, 18 Dec 2022 17:52:42 +0800) 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:251357 Archived-At: > From: Po Lu > Cc: karl@karlotness.com, 60144@debbugs.gnu.org > Date: Sun, 18 Dec 2022 17:52:42 +0800 > > > Why this fragile architecture of reading input events? Calling > > functions of our Lisp machine from context where those functions > > cannot signal an error is very dangerous, and cannot work well in > > Emacs. Why cannot we have the reads through GTK only deliver events > > to us, which we enqueue to our own event queue, and then we could > > process that queue in the safe context of the Lisp machine, as (AFAIK) > > we do on other platforms? > > No, signalling there is equally unsafe on the other platforms, where > note_mouse_highlight is called from the same place(s): read_socket_hook, > event_handler_gdk, et cetera. Just look at the callers of > x_note_mouse_movement in xterm.c, or [EmacsView mouseMoved:] in > nsterm.m. Sorry, I'm afraid I don't see the danger on other platforms. Please explain. AFAIK, read_socket_hook is called from keyboard.c code which reads input, and that code has no problem signaling an error. What am I missing?