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: Sun, 27 Feb 2005 23:36:18 +0100 Message-ID: References: <874qfxekpy.fsf-monnier+emacs@gnu.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1109543850 9306 80.91.229.2 (27 Feb 2005 22:37:30 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 27 Feb 2005 22:37:30 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Feb 27 23:37:30 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D5X2N-00013K-St for ged-emacs-devel@m.gmane.org; Sun, 27 Feb 2005 23:37:20 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D5XKc-0001fW-GU for ged-emacs-devel@m.gmane.org; Sun, 27 Feb 2005 17:56:10 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D5XGx-0007xF-E3 for emacs-devel@gnu.org; Sun, 27 Feb 2005 17:52:23 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D5XGu-0007wE-P7 for emacs-devel@gnu.org; Sun, 27 Feb 2005 17:52:21 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D5XGu-0007w1-HJ for emacs-devel@gnu.org; Sun, 27 Feb 2005 17:52:20 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D5X1d-0007rW-Vf for emacs-devel@gnu.org; Sun, 27 Feb 2005 17:36:34 -0500 Original-Received: from localhost ([127.0.0.1] helo=lola.goethe.zz) by fencepost.gnu.org with esmtp (Exim 4.34) id 1D5X1P-0001dX-89; Sun, 27 Feb 2005 17:36:19 -0500 Original-To: Stefan Monnier In-Reply-To: <874qfxekpy.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 27 Feb 2005 16:51:32 -0500") 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:33894 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:33894 Stefan Monnier writes: >> elusive is going on here. I'll probably have to implement some kind >> of trace buffering for interrupt_input_block in order to get a hold of >> what is happening here. > > If for some reason you think the problems you're experience have something > to do with interrupt_input_block, maybe you should try to recompile > with -DSYNC_INPUT. I'd rather get a hold of what happens. Fortunately, one can place something like #define BLOCK_INPUT do { __label__ zap; int i = tp++ & 255; \ zap: tb[i].adr = &&zap; tb[i].value = ++interrupt_input_blocked; \ while (0) into a header file. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum