Re: [O] Trouble evaluating R source code blocks with C-c C-c

[Charles C. Berry]

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).

Chuck