From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.bugs Subject: bug#1753: emacs may cause window manager to hang Date: Thu, 01 Jan 2009 04:19:05 -0500 Message-ID: <87ljtvs7sm.fsf@cyd.mit.edu> Reply-To: Chong Yidong , 1753@emacsbugs.donarmstrong.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1230803020 28518 80.91.229.12 (1 Jan 2009 09:43:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 1 Jan 2009 09:43:40 +0000 (UTC) Cc: 1753@emacsbugs.donarmstrong.com To: Paul Graham Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Jan 01 10:44:49 2009 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LIK6i-0003yN-V5 for geb-bug-gnu-emacs@m.gmane.org; Thu, 01 Jan 2009 10:44:49 +0100 Original-Received: from localhost ([127.0.0.1]:46876 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LIK5U-0001dG-0i for geb-bug-gnu-emacs@m.gmane.org; Thu, 01 Jan 2009 04:43:32 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LIK5O-0001d5-UH for bug-gnu-emacs@gnu.org; Thu, 01 Jan 2009 04:43:26 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LIK5N-0001cg-9a for bug-gnu-emacs@gnu.org; Thu, 01 Jan 2009 04:43:26 -0500 Original-Received: from [199.232.76.173] (port=35926 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LIK5N-0001cc-49 for bug-gnu-emacs@gnu.org; Thu, 01 Jan 2009 04:43:25 -0500 Original-Received: from rzlab.ucr.edu ([138.23.92.77]:35723) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LIK5M-00024h-IU for bug-gnu-emacs@gnu.org; Thu, 01 Jan 2009 04:43:24 -0500 Original-Received: from rzlab.ucr.edu (rzlab.ucr.edu [127.0.0.1]) by rzlab.ucr.edu (8.13.8/8.13.8/Debian-3) with ESMTP id n019hMVs021181; Thu, 1 Jan 2009 01:43:22 -0800 Original-Received: (from debbugs@localhost) by rzlab.ucr.edu (8.13.8/8.13.8/Submit) id n019P4PL016395; Thu, 1 Jan 2009 01:25:04 -0800 X-Loop: owner@emacsbugs.donarmstrong.com Resent-From: Chong Yidong Resent-To: bug-submit-list@donarmstrong.com Resent-CC: Emacs Bugs Resent-Date: Thu, 01 Jan 2009 09:25:03 +0000 Resent-Message-ID: Resent-Sender: owner@emacsbugs.donarmstrong.com X-Emacs-PR-Message: followup 1753 X-Emacs-PR-Package: emacs X-Emacs-PR-Keywords: Original-Received: via spool by 1753-submit@emacsbugs.donarmstrong.com id=B1753.123080154415032 (code B ref 1753); Thu, 01 Jan 2009 09:25:03 +0000 Original-Received: (at 1753) by emacsbugs.donarmstrong.com; 1 Jan 2009 09:19:04 +0000 X-Spam-Bayes: score:0.5 Bayes not run. spammytokens:Tokens not available. hammytokens:Tokens not available. Original-Received: from cyd.mit.edu (CYD.MIT.EDU [18.115.2.24]) by rzlab.ucr.edu (8.13.8/8.13.8/Debian-3) with ESMTP id n019J2DH015026 for <1753@emacsbugs.donarmstrong.com>; Thu, 1 Jan 2009 01:19:03 -0800 Original-Received: by cyd.mit.edu (Postfix, from userid 1000) id 3B47157E211; Thu, 1 Jan 2009 04:19:05 -0500 (EST) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) Resent-Date: Thu, 01 Jan 2009 04:43:26 -0500 X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:23649 Archived-At: Unfortunately, judging by past bugs related to multi-screen setups, none of the regular Emacs bug-fixers have multiple screens available for reproducing such bugs. I suggest running Emacs under gdb in an xterm, and arranging things so that when focus gets stuck, that xterm is in focus. Assuming that's possible, do C-z to suspend the Emacs process, and inspect the backtrace to see if anything suspicious is going on; maybe Emacs is looping somewhere in its window-manager interaction code?