Displaying 3 results from an estimated 3 matches for "jump_to_toplevel".
2000 Nov 07
0
error handling
...)) // R_ToplevelContext->cjmpbuf
R_GlobalContext->cjmpbuf
return FALSE;
R_CurrentExpr = eval(R_CurrentExpr , rho);
will appear to work the first time there is an error, but the second error
causes an infinite loop. I have identified the location where the loop
occurs. It is in the function jump_to_toplevel() in errors.c inside the for
loop:
for (c = R_GlobalContext; c; c = c->nextcontext) { ... }
I have found a work around for this but is seems cludgy and I don't know the
POTENTIAL PROBLEMS that might be introduced. It involves setting up a
context and forcing R_GlobalContext's nextcont...
2001 Aug 20
2
interrupting Sys.sleep (PR#1063)
On Linux R1.3.0 (and current pre1.3.1 and pre1.4.0)
Sys.sleep(30)
interrupt with CTRL-C
Sys.sleep(30)
causes a segmentation fault. It doesn't happen under Windows (2000).
-thomas
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or
1997 Apr 28
3
R-alpha: R-0.49: 2 problems
I found the following 2 problems (no debugging, sorry).
* qt(0.975, 3) never returns.
Can someone please check that? Happens for me on Debian GNU/Linux/ix86
compiled with CFLAGS="-O2 -g".
* Yet another stupid way to cause a segfault:
R> x
Error: Object "x" not found
R> debug(t.test)
R> t.test(rnorm(10))
debug: choices <- c("two.sided",