Displaying 6 results from an estimated 6 matches for "r_evaldepth".
2000 Feb 14
1
Problem with expression evaluation depth (PR#436)
...in the expression evaluation
depth.
The problem appears in a program with no recursions
whatsoever. The layout of my program is a series
of routines called by a big loop.
I printed out depthsave in src/main/eval.c
and it appears as there is an error popping out
the length of the expression stack, R_EvalDepth,
somewhere. As the loop goes, R_EvalDepth goes up
and down, but in average, it alway increases.
For the moments, I commented out the check with
options$expression and my program finished succesfully.
Any help would be appreciated.
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-....
2009 Mar 03
1
profiler and loops
...ext of the for loop. The
begincontext function looks like this :
void begincontext(RCNTXT * cptr, int flags,
SEXP syscall, SEXP env, SEXP sysp,
SEXP promargs, SEXP callfun)
{
cptr->nextcontext = R_GlobalContext;
cptr->cstacktop = R_PPStackTop;
cptr->evaldepth = R_EvalDepth;
cptr->callflag = flags;
cptr->call = syscall;
cptr->cloenv = env;
cptr->sysparent = sysp;
cptr->conexit = R_NilValue;
cptr->cend = NULL;
cptr->promargs = promargs;
cptr->callfun = callfun;
cptr->vmax = vmaxget();
cptr->intsusp = R_interru...
2020 Jun 25
0
R 4.0.1-4.0.2 built with Intel Composer 19.0-19.1.1, error in "make check" on CentOS 7.7
...s (traceback() being more than 2500 entries long) seems to imply
that the stack size check is somehow skipped. (Perhaps optimized away?)
The evaluation depth limit is checked in src/main/eval.c, line 705 [*],
followed by stack size check. Can you attach the debugger and take a
look at the values of R_EvalDepth and R_Expressions while executing the
text? What about R_CStackStart and R_CStackLimit? What is the stack
size limit (ulimit -s?) on the machine running this test?
--
Best regards,
Ivan
[*]
https://github.com/wch/r-source/blob/8d7ac4699fba640d030703fa010b66bf26054cbd/src/main/eval.c#L705
------...
2000 Feb 16
0
Fwd: Re: Problem with expression evaluation depth (PR#436)
Jose Miguel Perez <jperez@cesma.usb.ve> writes:
> I think I found the root of the problem.
> My program throws out some cycles of the loop
> using 'next'.
> The following code shows the behavior of R_EvalDepth in these cases:
> without next:
> > for (i in 1:10 ) {}
> 0
> 1
> 2
> 2
> 1
> 1
> 1
> 1
> 1
> 1
> 1
>
> with next:
> > for (i in 1:10 ) {next}
> 0
> 1
> 2
> 2
> 1
> 2
> 3
> 4
> 5
> 6
> 7
> 8
> 9
> 10
&g...
2007 Jan 18
0
Emulating a REPL in frontends
...amp;status);
if(parse_status) *parse_status = status;
switch(status) {
case PARSE_NULL:
R_IoBufferWriteReset(&R_ConsoleIob);
break;
case PARSE_OK:
R_IoBufferReadReset(&R_ConsoleIob);
R_CurrentExpr = R_Parse1Buffer(&R_ConsoleIob, 1, &status);
R_Visible = FALSE;
R_EvalDepth = 0;
PROTECT(R_CurrentExpr);
R_Busy(1);
value = eval(R_CurrentExpr, rho);
if(set_last_sym_value)
SET_SYMVALUE(R_LastvalueSymbol, value);
if ((print_mode==1) || (R_Visible && (print_mode==0)))
wasDisplayed = TRUE;
PrintValueEnv(R_CurrentExpr, rho);
if (R_CollectWarnings)...
2020 Jun 24
5
R 4.0.1-4.0.2 built with Intel Composer 19.0-19.1.1, error in "make check" on CentOS 7.7
Hi there,
I initially asked about this on r-help and was told this might be a better venue. I?m not really convinced from reading the posting guide, but I?ll give it a shot. It was also suggested that the R-Project doesn?t really care about building with ?non-standard? compilers, but I can?t find any evidence of that on the website (indeed, there?s some mention of successful past builds, and the