From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: Some experience with the igc branch Date: Thu, 26 Dec 2024 15:29:29 -0800 Organization: UCLA Computer Science Department Message-ID: References: <87o713wwsi.fsf@telefonica.net> <87ldw6as5f.fsf@protonmail.com> <86o7112rnq.fsf@gnu.org> <867c7p2nz4.fsf@gnu.org> <861pxx2lh7.fsf@gnu.org> <86ldw40xbo.fsf@gnu.org> <86a5cj2a0e.fsf@gnu.org> <867c7n28sf.fsf@gnu.org> <877c7n962e.fsf@gmail.com> <8634ib24gp.fsf@gnu.org> <875xn75w7u.fsf@gmail.com> <86ttaryn1x.fsf@gnu.org> <877c7mzxbw.fsf@gmail.com> <861pxuzt61.fsf@gnu.org> <87wmfmy6mq.fsf@gmail.com> <86ttaqxybk.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30309"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla Thunderbird Cc: gerd.moellmann@gmail.com, pipcet@protonmail.com, emacs-devel@gnu.org To: Eli Zaretskii , Helmut Eller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Dec 27 00:30:15 2024 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 1tQxJ1-0007j5-2R for ged-emacs-devel@m.gmane-mx.org; Fri, 27 Dec 2024 00:30:15 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tQxIO-0002yG-VX; Thu, 26 Dec 2024 18:29:37 -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 1tQxIM-0002y6-NF for emacs-devel@gnu.org; Thu, 26 Dec 2024 18:29:34 -0500 Original-Received: from mail.cs.ucla.edu ([131.179.128.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tQxIK-0001jh-Nt; Thu, 26 Dec 2024 18:29:34 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by mail.cs.ucla.edu (Postfix) with ESMTP id 152F53C082C8C; Thu, 26 Dec 2024 15:29:30 -0800 (PST) Original-Received: from mail.cs.ucla.edu ([127.0.0.1]) by localhost (mail.cs.ucla.edu [127.0.0.1]) (amavis, port 10032) with ESMTP id MfOG1I6iStmK; Thu, 26 Dec 2024 15:29:29 -0800 (PST) Original-Received: from localhost (localhost [127.0.0.1]) by mail.cs.ucla.edu (Postfix) with ESMTP id C36E03C082EA5; Thu, 26 Dec 2024 15:29:29 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.cs.ucla.edu C36E03C082EA5 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.ucla.edu; s=9D0B346E-2AEB-11ED-9476-E14B719DCE6C; t=1735255769; bh=6Z/kXKo2n4XB7KgVSXEVrwX8tlkf8PgH5reaurSHp+g=; h=Message-ID:Date:MIME-Version:To:From; b=EkAgbdJm5/47dl2Ux8yLTANQITHnzWoS31K2dwGeU6R9GgrbTxDikEDyTcNTUamU3 sikTD/9vd9Viqmkg2lDSFKXXX4LJnqNPL6Iw9R/2WYQklh2Ktm/fv4E4VuhDeClom3 EZ+yF7Y6z+1VrzAiqP6qFicKk8+HLK1zFPlh94kQoGnDKr9vc5JXDpO+NTYwMqS3p4 Ntgbmz8Ug2+5lzVgUHNbhzvy4okViIFTnUwvb0wE5o0IKCRlfRsJ3IQLHgpXGbWr9R +vPCGGYqsuG74U7WC26c8ErpsumiYy15rbKGvvwwrD5kTosmEdh3o4xf9MN3nJISSO tE3MZlasxnVPw== X-Virus-Scanned: amavis at mail.cs.ucla.edu Original-Received: from mail.cs.ucla.edu ([127.0.0.1]) by localhost (mail.cs.ucla.edu [127.0.0.1]) (amavis, port 10026) with ESMTP id azXz34enrpfA; Thu, 26 Dec 2024 15:29:29 -0800 (PST) Original-Received: from [192.168.254.12] (unknown [47.154.28.214]) by mail.cs.ucla.edu (Postfix) with ESMTPSA id 9ED123C082C8C; Thu, 26 Dec 2024 15:29:29 -0800 (PST) Content-Language: en-US In-Reply-To: <86ttaqxybk.fsf@gnu.org> Received-SPF: pass client-ip=131.179.128.66; envelope-from=eggert@cs.ucla.edu; helo=mail.cs.ucla.edu X-Spam_score_int: -19 X-Spam_score: -2.0 X-Spam_bar: -- X-Spam_report: (-2.0 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:327171 Archived-At: On 2024-12-26 07:23, Eli Zaretskii wrote: >> From: Helmut Eller >> I thought deliver_process_signal was there to forward signals to the >> main thread but you certainly know better what it does and doesn't. > > Actually, we need Paul Eggert to chime in, because he knows much more > about this than I do. We have arrangements for when a signal is > delivered to a thread, but I think Paul said this should rarely if > ever happen. Helmut's right: deliver_process_signal arranges for the handler to be called in the main thread even if the thread was delivered to some other thread. And to some extent you're right, too, on GNU/Linux, where historically this rarely happened unless the signal was blocked in the main thread. That part of the Linux kernel has evolved, though, and I don't know whether this is still true. However, whether it's true shouldn't affect the correctness of deliver_process_signal.