Displaying 4 results from an estimated 4 matches for "jump_now".
2003 Oct 27
1
Rpy Import Error
...ks, Brett
>>> import rpy
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "/usr/lib/python2.2/site-packages/rpy.py",
line 24, in ?
import _rpy
ImportError:
/usr/lib/python2.2/site-packages/_rpymodule.so:
undefined symbol: jump_now
>>>
I have R-1.8.0 installed as a shared library on a
linux 2.4.22 (slackware 9.1) system, compiled on my
machine with GCC 3.2.3. I have the most recent
version (0.3.1) of Rpy and python 2.3.1.
2003 Sep 13
1
R 1.8.0 (to be) and RPy 0.3.1
...re -- initially an Atlas interaction,
currently something with long_jump() which cannot be found when R's dynamic
library is loaded. [1] It is called R_eval.c:
/* Abort the current R computation and signal a KeyboardInterrupt
exception */
void interrupt_R(int signum)
{
interrupted = 1;
jump_now();
}
By commenting it out, the package builds and is usable (modulo the absence
of interrupt handling, I suppose).
Could someone give me a pointer or suggestion as to what the replacement for
jump_now() would be?
Dirk
[1] See e.g. http://www.togaware.com/linux/survivor/In...
2002 Jun 27
0
1.5.1 docs on handling errors when embedding R ?
Hello all,
I have a system in which I embed R, currently it
is running using 1.3.1 release, and I would like to
upgrade to 1.5.1.
I need to trap and report any errors during evaluation.
Previously I was installing my own ErrorHook to capture
error messages and over-riding jump_now to call
Rf_resetStack(1). I know there has been some massive work
in this area so things have changed (i.e. my old code doesn't
compile ). I am sure I can figure it out by looking
at the code, but are there some docs somewhere about this stuff ?
Thanks,
Bruno
PS: great work, embedding R is...
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",