From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Charles C. Berry" Subject: Re: Trouble evaluating R source code blocks with C-c C-c Date: Sat, 28 May 2016 10:01:41 -0700 Message-ID: References: <2BE21056-50D3-49CE-8B0D-5467D182B7B5@agrarianresearch.org> <2E8B017B-F4AB-454D-81A1-E61F55F4F958@agrarianresearch.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40128) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b6hcS-0008Px-GJ for emacs-orgmode@gnu.org; Sat, 28 May 2016 13:01:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b6hcN-0003Ar-Ep for emacs-orgmode@gnu.org; Sat, 28 May 2016 13:01:47 -0400 Received: from iport-bcv1-out.ucsd.edu ([132.239.0.119]:30353) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b6hcN-0003AX-8P for emacs-orgmode@gnu.org; Sat, 28 May 2016 13:01:43 -0400 In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: William Denton Cc: org-mode mailing list , Vikas Rawal p.s. one more thing - below On Sat, 28 May 2016, Charles C. Berry wrote: > On Sat, 28 May 2016, William Denton wrote: > >> On 28 May 2016, Vikas Rawal wrote: >> >>> Thanks John. Appreciate that you cared to respond to such a vague query. I >>> am at a loss with this one. It does not happen all the time. I think it >>> happens when I am processing large datasets, and CPUs and RAM of my system >>> are struggling to keep up. But I could be wrong. >> >> I've had the same kind of thing happen---but C-g (sometimes many) to kill >> the command, then rerunning, usually works without any trouble. Some >> strange combination of CPU and RAM and all that, the kind of thing that's >> not easily reproducible. >> > > Try this: customize `debug-on-quit' to `t' (and set for current session). > > Then when you have to quit via C-g, you will get a backtrace showing where > the process was hanging and how it got there. This might be helpful in > figuring out what is going on. > > Run your code and when you finally have to C-g out copy the *Backtrace* > buffer and report it back here (or on the ESS list if appropriate). > After you copy the buffer, you should type 'q' in the *Backtrace* buffer to finish up or you may have some odd messages and hangups afterwards. Chuck