From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Jan D." Newsgroups: gmane.emacs.devel Subject: Re: Core dumps in redisplay. Date: Mon, 28 Feb 2005 18:15:25 +0100 Message-ID: <854df3d393258d420a5f4a60c87f6ea0@swipnet.se> References: <7eee8e4a0b7241b67a0ae97e4923b908@swipnet.se> <49e5a9dfdc9abedb548ffb2ba94ee4bb@swipnet.se> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1109612085 11789 80.91.229.2 (28 Feb 2005 17:34:45 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 28 Feb 2005 17:34:45 +0000 (UTC) Cc: Emacs Devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 28 18:34:45 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D5okt-0002Hf-3m for ged-emacs-devel@m.gmane.org; Mon, 28 Feb 2005 18:32:28 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D5p3H-0008Ll-GY for ged-emacs-devel@m.gmane.org; Mon, 28 Feb 2005 12:51:27 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D5p0f-0006xB-Ah for emacs-devel@gnu.org; Mon, 28 Feb 2005 12:48:45 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D5p0d-0006vt-DA for emacs-devel@gnu.org; Mon, 28 Feb 2005 12:48:44 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D5oxc-00053k-SL for emacs-devel@gnu.org; Mon, 28 Feb 2005 12:45:36 -0500 Original-Received: from [195.54.107.70] (helo=mxfep01.bredband.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D5oUb-0007tz-MY; Mon, 28 Feb 2005 12:15:38 -0500 Original-Received: from coolsville.localdomain ([83.226.180.210] [83.226.180.210]) by mxfep01.bredband.com with ESMTP id <20050228171536.DZHU429.mxfep01.bredband.com@coolsville.localdomain>; Mon, 28 Feb 2005 18:15:36 +0100 In-Reply-To: Original-To: David Kastrup X-Mailer: Apple Mail (2.619.2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org X-MailScanner-To: ged-emacs-devel@m.gmane.org Xref: main.gmane.org gmane.emacs.devel:33938 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:33938 > "Jan D." writes: > >>> >>> This sounds like normally only the main thread should ever be >>> touching >>> interrupt_input_blocked, unless we have a bug. Correct? So we need >>> not think about how to synchronize accesses to the variable, but >>> rather make sure that no thread except the main thread will ever run >>> code touching it. Correct? >>> >>> A use of BLOCK_INPUT or UNBLOCK_INPUT outside of the main thread is a >>> bug. Correct? >> >> Yes times three. > > xmalloc uses BLOCK_INPUT. BLOCK_INPUT is rather often used in alloc.c. Yes, there is a check for main thread there also, see macros (UN)BLOCK_INPUT_ALLOC. Jan D.