From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Richard M. Stallman" Newsgroups: gmane.emacs.devel Subject: Re: allocate_string_data memory corruption Date: Fri, 20 Jan 2006 17:58:01 -0500 Message-ID: References: <87vewha2zl.fsf@stupidchicken.com> <87wtgxdr9p.fsf@stupidchicken.com> <873bjkha3d.fsf@pacem.orebokech.com> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1137802105 12470 80.91.229.2 (21 Jan 2006 00:08:25 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 21 Jan 2006 00:08:25 +0000 (UTC) Cc: cyd@stupidchicken.com, romain@orebokech.com, emacs-devel@gnu.org, raeburn@raeburn.org, storm@cua.dk Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 21 01:08:24 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1F06Ij-0004LF-Uj for ged-emacs-devel@m.gmane.org; Sat, 21 Jan 2006 01:08:18 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F06LE-0008HD-9O for ged-emacs-devel@m.gmane.org; Fri, 20 Jan 2006 19:10:52 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1F05IT-0005bc-44 for emacs-devel@gnu.org; Fri, 20 Jan 2006 18:03:57 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1F05IR-0005Z8-9D for emacs-devel@gnu.org; Fri, 20 Jan 2006 18:03:55 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F05IP-0005Yc-FT for emacs-devel@gnu.org; Fri, 20 Jan 2006 18:03:53 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1F05Mh-0004Gm-6f for emacs-devel@gnu.org; Fri, 20 Jan 2006 18:08:19 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1F05Cj-0005PM-7q; Fri, 20 Jan 2006 17:58:01 -0500 Original-To: Stefan Monnier In-reply-to: (message from Stefan Monnier on Thu, 19 Jan 2006 22:46:03 -0500) 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 Xref: news.gmane.org gmane.emacs.devel:49336 Archived-At: Huh? Where did you get this idea? Events get processed as soon as we hit a QUIT or a UNBLOCK_INPUT, which is a lot more frequent than reading input. I've been using -DSYNC_INPUT without noticing any detrimental effect for more than year. I apologize for my fallible memory--that is what I remembered. I guess the real issue is this one with C-g. processing of C-g since we then processs signals with a "polling" model (if we get stuck in a loop with no QUIT and no BLOCK_INPUT we won't ever process the C-g. It seems to be that even without SYNC_INPUT, under X11, a C-g is not process until we reach a QUIT, so the difference is not clear to me). Many loops in Emacs use immediate_quit rather than QUIT. If quitting out of them does not work, it is a serious problem. One possible fix would be to get rid of immediate_quit, and use QUIT in every loop.