Well, if you are already using R_tryEval then it is (should be) catching
the error already and the problem is something else but I can't tell what
it is with the information you've posted.
~G
On Tue, Feb 25, 2014 at 1:09 PM, Sandip Nandi wrote:
> Hi ,
>
> I am using R_tryEval . Is there any wa
Hi ,
I am using R_tryEval . Is there any way to handle the error ?
Thanks
On Tue, Feb 25, 2014 at 1:04 PM, Gabriel Becker wrote:
> Sandip,
>
>
> Are you doing R_eval (sp?) or R_tryEval? Uncaught R-level errors during
> C-level evaluation can cause segfaults IIRC.
>
> ~G
>
>
> On Tue, Feb 25, 2
Sandip,
Are you doing R_eval (sp?) or R_tryEval? Uncaught R-level errors during
C-level evaluation can cause segfaults IIRC.
~G
On Tue, Feb 25, 2014 at 12:00 PM, Sandip Nandi wrote:
> Hi ,
>
> I am running R from C using the interpreter . Now i
> execute detach("package:td", unload=TRUE)
> An
Hi ,
I am running R from C using the interpreter . Now i
execute detach("package:td", unload=TRUE)
And I get the following error . Any idea what it means ?
*** caught segfault ***
address 0x102, cause 'memory not mapped'
Traceback:
1: sys.parent()
2: sys.function(sys.parent())
3: formals(s
