I can reproduce it with python-2.5 / R-2.6.1 as well.
The error might well only have to do with X11 devices only, so
I wanted to try R-2.7.0 (since it will/should be using cairo devices
by default), but no luck: I already get error a RunTime error at load
time :-/ .
On the other end, I managed to
I've been experiencing this error with several versions of rpy. The only
version that did work properly was Rpy1RC3, however newer versions of R
require newer versions of Rpy, and I had to update to a newer Rpy and
survive with the error. I've heard that this issue only arises on *nix
systems
On Wed, Apr 9, 2008 at 3:26 AM, Laurent Gautier <[EMAIL PROTECTED]> wrote:
> Issues with the C stack are encountered now and then, and this might
> be a problem
> with R:
> http://tolstoy.newcastle.edu.au/R/e4/help/08/01/2069.html
>
> More generally, whenever the host application (here the Pyth
Issues with the C stack are encountered now and then, and this might
be a problem
with R:
http://tolstoy.newcastle.edu.au/R/e4/help/08/01/2069.html
More generally, whenever the host application (here the Python
process) is manipulating the stack (like when using threads I think)
the problem might
I get these sorts of memory errors (sometimes a segfault, sometimes a
bus error) too, a fair amount, when plotting in RPy. Nothing else,
just plotting. I don't have any idea what's going on either, but I'd
sure like to know how to stop it from happening.
---
