From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Help: exporting an agenda view not working in v6.31a Date: Thu, 15 Oct 2009 18:15:43 -0400 Message-ID: <14516.1255644943@gamaville.dokosmarshall.org> References: Reply-To: nicholas.dokos@hp.com Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MyYdS-0001w6-5L for emacs-orgmode@gnu.org; Thu, 15 Oct 2009 18:17:26 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MyYdN-0001n4-ES for emacs-orgmode@gnu.org; Thu, 15 Oct 2009 18:17:25 -0400 Received: from [199.232.76.173] (port=45673 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MyYdN-0001n1-AC for emacs-orgmode@gnu.org; Thu, 15 Oct 2009 18:17:21 -0400 Received: from vms173019pub.verizon.net ([206.46.173.19]:41131) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MyYdN-0005ME-0D for emacs-orgmode@gnu.org; Thu, 15 Oct 2009 18:17:21 -0400 Received: from gamaville.dokosmarshall.org ([98.110.172.159]) by vms173019.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPA id <0KRK003V6TU5VRL7@vms173019.mailsrvcs.net> for emacs-orgmode@gnu.org; Thu, 15 Oct 2009 17:15:41 -0500 (CDT) In-reply-to: Message from Qi Qi of "Thu, 15 Oct 2009 16:43:55 CDT." List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Qi Qi Cc: orgmode emacs Qi Qi wrote: > Thanks, Nick. I will see if backtrace could give it any clues. > > C-g doesn't work after my emacs hangs. When I type C-x C-w in the > agenda view, and selet an option to export then it hangs there. I can > see the cpu jumps high for long. > > It's strange. Because I did exactly same thing in v6.30g without such problem. > How do you get out of it? Do you restart emacs? If C-g does not work, then you are not going to be able to get a backtrace in these circumstances. You *might* be able to use edebug-defun to single-step through the called functions and find out where it hangs (it's tedious, but...) What machine/OS are you running? Which version of emacs? Assuming Linux, does top indicate that emacs is taking up all the CPU? Or is it some other process? top, ps, vmstat, iostat and so on are all useful in getting a glimpse into what's happening. Good luck, Nick