From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Core dumps in redisplay. Date: Mon, 28 Feb 2005 11:38:52 +0100 Message-ID: References: <7eee8e4a0b7241b67a0ae97e4923b908@swipnet.se> <49e5a9dfdc9abedb548ffb2ba94ee4bb@swipnet.se> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1109592543 4186 80.91.229.2 (28 Feb 2005 12:09:03 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 28 Feb 2005 12:09:03 +0000 (UTC) Cc: Emacs Devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 28 13:09:02 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D5jhi-0008No-VI for ged-emacs-devel@m.gmane.org; Mon, 28 Feb 2005 13:08:51 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D5k04-0006Hv-90 for ged-emacs-devel@m.gmane.org; Mon, 28 Feb 2005 07:27:48 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D5ian-0003oy-Qf for emacs-devel@gnu.org; Mon, 28 Feb 2005 05:57:39 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D5iaT-0003mz-Sy for emacs-devel@gnu.org; Mon, 28 Feb 2005 05:57:31 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D5iaP-0003mj-SH for emacs-devel@gnu.org; Mon, 28 Feb 2005 05:57:14 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D5iIf-00042n-Rd for emacs-devel@gnu.org; Mon, 28 Feb 2005 05:38:53 -0500 Original-Received: from localhost ([127.0.0.1] helo=lola.goethe.zz) by fencepost.gnu.org with esmtp (Exim 4.34) id 1D5iIf-0002JT-7X; Mon, 28 Feb 2005 05:38:53 -0500 Original-To: "Jan D." In-Reply-To: <49e5a9dfdc9abedb548ffb2ba94ee4bb@swipnet.se> (Jan D.'s message of "Mon, 28 Feb 2005 06:34:30 +0100") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) 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:33912 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:33912 "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. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum