On 5/7/07, Deepayan Sarkar <deepayan.sarkar at gmail.com> wrote:
On 5/6/07, Deepayan Sarkar <deepayan.sarkar at gmail.com> wrote:
I will have to start learning about gdb sometime soon, but in this case,
the
problem seems to be due to the interaction of R_tryEval() and graphics, and has nothing to do with interruptions. Here's a variant of the trEval test case that triggers a legitimate error caused by
[...] Turns out R_tryEval is not to blame; the error (here as well as in my GUI) was occurring inside the unprotected call to PrintValue() after tryEval returned. I should have noticed that sooner. Sorry for the noise. -Deepayan