From deepayan.sarkar at gmail.com  Tue May  8 07:55:02 2007
From: deepayan.sarkar at gmail.com (deepayan.sarkar at gmail.com)
Date: Tue, 8 May 2007 00:55:02 -0500
Subject: [Rd] sending signals to embedded R [SOLVED]
Message-ID: <eb555e660705072255g4bd7f400g4d1fe8758c847820@mail.gmail.com>

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



[Rd] sending signals to embedded R [SOLVED]
deepayan.sarkar at gmail.com