From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Michael Heerdegen Newsgroups: gmane.emacs.help Subject: Re: help! Keep getting emacs locked up / not responding to c-g / having to kill process Date: Thu, 03 Oct 2013 17:44:22 +0200 Message-ID: <87ob761hrd.fsf@web.de> References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1380815103 13229 80.91.229.3 (3 Oct 2013 15:45:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 3 Oct 2013 15:45:03 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Oct 03 17:45:05 2013 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VRl5M-0008Hz-Mq for geh-help-gnu-emacs@m.gmane.org; Thu, 03 Oct 2013 17:45:04 +0200 Original-Received: from localhost ([::1]:43880 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VRl5M-0004Tc-DH for geh-help-gnu-emacs@m.gmane.org; Thu, 03 Oct 2013 11:45:04 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55017) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VRl52-0004KY-RP for help-gnu-emacs@gnu.org; Thu, 03 Oct 2013 11:44:50 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VRl4v-0003zz-MP for help-gnu-emacs@gnu.org; Thu, 03 Oct 2013 11:44:44 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:34948) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VRl4v-0003zX-GK for help-gnu-emacs@gnu.org; Thu, 03 Oct 2013 11:44:37 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VRl4t-0007vp-PD for help-gnu-emacs@gnu.org; Thu, 03 Oct 2013 17:44:35 +0200 Original-Received: from ip-90-187-177-228.web.vodafone.de ([90.187.177.228]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 03 Oct 2013 17:44:35 +0200 Original-Received: from michael_heerdegen by ip-90-187-177-228.web.vodafone.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 03 Oct 2013 17:44:35 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 18 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip-90-187-177-228.web.vodafone.de User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:4t1jC7NKN8KJroe/gdIkcTCbTbw= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:93814 Archived-At: unfrostedpoptart writes: > However, lately (including 15 minutes ago) I've been hitting this and > c-g does nothing and ps shows emacs at around 95% cpu. As this is a > shared server, that doesn't make me popular with other users! As Drew mentioned, it's hard to guess who the culprit is without more details (recipe). Anyway, in Unices you can force Emacs into the debugger, even if not responsive, by sending SIGUSR2: pkill -SIGUSR2 emacs Using the debugger, you hopefully should be able to see where Emacs loops. Michael.