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: Sun, 29 Jan 2006 19:57:26 -0500 Message-ID: References: <87vewha2zl.fsf@stupidchicken.com> <87zmlq6w62.fsf-monnier+emacs@gnu.org> <874q3v6a65.fsf-monnier+emacs@gnu.org> <873bjbahq6.fsf@stupidchicken.com> <87r76usumg.fsf-monnier+emacs@gnu.org> <871wyuixit.fsf@stupidchicken.com> <87slr7k4ub.fsf@stupidchicken.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 1138583254 4554 80.91.229.2 (30 Jan 2006 01:07:34 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 30 Jan 2006 01:07:34 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 30 02:07:32 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 1F3NVv-0003OR-RJ for ged-emacs-devel@m.gmane.org; Mon, 30 Jan 2006 02:07:28 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F3NYq-00015N-K7 for ged-emacs-devel@m.gmane.org; Sun, 29 Jan 2006 20:10:29 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1F3NPt-0005l1-HU for emacs-devel@gnu.org; Sun, 29 Jan 2006 20:01:14 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1F3NPr-0005kR-N8 for emacs-devel@gnu.org; Sun, 29 Jan 2006 20:01:12 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F3NPr-0005kI-Bo for emacs-devel@gnu.org; Sun, 29 Jan 2006 20:01:11 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.52) id 1F3NO4-0006YE-Ot for emacs-devel@gnu.org; Sun, 29 Jan 2006 19:59:20 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1F3NME-0000OX-FB; Sun, 29 Jan 2006 19:57:26 -0500 Original-To: Chong Yidong In-reply-to: <87slr7k4ub.fsf@stupidchicken.com> (message from Chong Yidong on Sat, 28 Jan 2006 23:58:36 -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:49726 Archived-At: > I don't see any better solution. It is non-trivial to fix the > behavior of handle_one_xevent with synched input. I, for one, don't > see any clean way to fix note_mouse_highlight and > x_handle_dnd_message. Perhaps there is a misunderstanding. You said it was hard to fix these "with synched input". So I thought you were talking about problems in SYNC_INPUT. But your response now seems to refer to the problems that we have recently observed _without_ SYNC_INPUT. We already discussed the note_mouse_highlight problem somewhat. Basically, it can lead to calling realize_face for a mouse face, which can call allocate_vectorlike and make_uninit_multibyte_string. I don't know how to avoid this, since the mouse face is constructed on the fly by merging overlay and text property mouse faces. Using SYNC_INPUT would fix that, wouldn't it? And I think it would fix those other two problems, too. So, do you know of any problems in SYNC_INPUT aside from not handling immediate_quit?