From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: Suspicious error in GTk Date: Mon, 11 Jun 2007 16:37:43 -0400 Message-ID: <871wgixm5k.fsf@stupidchicken.com> References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1181594285 22420 80.91.229.12 (11 Jun 2007 20:38:05 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 11 Jun 2007 20:38:05 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 11 22:38:03 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HxqeJ-0002Rk-GS for ged-emacs-devel@m.gmane.org; Mon, 11 Jun 2007 22:38:03 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HxqeI-0005jK-Uw for ged-emacs-devel@m.gmane.org; Mon, 11 Jun 2007 16:38:03 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HxqeD-0005fU-CJ for emacs-devel@gnu.org; Mon, 11 Jun 2007 16:37:57 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HxqeB-0005bR-D4 for emacs-devel@gnu.org; Mon, 11 Jun 2007 16:37:55 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HxqeB-0005b9-7Z for emacs-devel@gnu.org; Mon, 11 Jun 2007 16:37:55 -0400 Original-Received: from cyd.mit.edu ([18.115.2.24]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HxqeA-000657-SE for emacs-devel@gnu.org; Mon, 11 Jun 2007 16:37:54 -0400 Original-Received: by cyd.mit.edu (Postfix, from userid 1000) id 57DDB4E50F; Mon, 11 Jun 2007 16:37:43 -0400 (EDT) In-Reply-To: (Stefan Monnier's message of "Mon\, 11 Jun 2007 16\:19\:56 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1.50 (gnu/linux) X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) 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:72646 Archived-At: Stefan Monnier writes: > While trying out SYNC_INPUT with Gtk together with the `eassert' debugging > I bumped into the appended backtrace, right at startup. Basically, the code > run from XTread_socket (run asynchronously at any time) can call > update_frame_tool_bar which in turn calls xpm_load which ends up calling > encode_coding_string (to encode the file's name) which fiddles with > specpdl_ptr (via record_unwind_protect) and may run elisp code. > > Most likely it will usually not lead to any problem, but I believe it'll > bite every now and then and will be difficult to trace. ISTR that parts of alloc.c are carried out inside BLOCK_INPUT, but only if SYNC_INPUT is off. Does this mean that we need BLOCK_INPUT even when SYNC_INPUT is on?