From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: unfrostedpoptart Newsgroups: gmane.emacs.help Subject: Re: help! Keep getting emacs locked up / not responding to c-g / having to kill process Date: Mon, 7 Oct 2013 15:31:19 -0700 (PDT) Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: ger.gmane.org 1381185315 32278 80.91.229.3 (7 Oct 2013 22:35:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 7 Oct 2013 22:35:15 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Oct 08 00:35:19 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 1VTJOY-0003Td-Pf for geh-help-gnu-emacs@m.gmane.org; Tue, 08 Oct 2013 00:35:19 +0200 Original-Received: from localhost ([::1]:33711 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VTJOY-000248-4B for geh-help-gnu-emacs@m.gmane.org; Mon, 07 Oct 2013 18:35:18 -0400 X-Received: by 10.66.102.69 with SMTP id fm5mr8170308pab.24.1381185079868; Mon, 07 Oct 2013 15:31:19 -0700 (PDT) X-Received: by 10.50.127.229 with SMTP id nj5mr846660igb.2.1381185079814; Mon, 07 Oct 2013 15:31:19 -0700 (PDT) Original-Path: usenet.stanford.edu!z6no46053523pbz.1!news-out.google.com!z6ni82374pbu.0!nntp.google.com!z6no46053518pbz.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=198.70.193.19; posting-account=S61AnQkAAADt4_PSYpI-Tm-z1E4cd7xa Original-NNTP-Posting-Host: 198.70.193.19 User-Agent: G2/1.0 Injection-Date: Mon, 07 Oct 2013 22:31:19 +0000 Original-Xref: usenet.stanford.edu gnu.emacs.help:201608 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:93878 Archived-At: On Thursday, October 3, 2013 8:44:22 AM UTC-7, Michael Heerdegen wrote: > 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. I'm hitting this right now. In this case, it was triggered by opening a PDF file. It started rendering but apparently hung up somewhere. Running pkill -SIGUSR2 did eventually appear to get control back and displayed the backtrace buffer but when I'd try and do anything, it would lock up again. After several pkills, I was able to get a buffer list and kill the PDF buffer. I'm not really up on using backtrace, but FYI, here's what it says: Debugger entered--entering a function: * linum-update-current() recursive-edit() debug(error (quit)) redisplay_internal\ \(C\ function\)() Not sure if there's anything I can do now to help trace it but if there is, please let me know. David