similar to: C stack usage is too close to the limit

Hi, I have been using my own C++ plugin for a while. On a new machine I now keep getting the C stack usage is too close to the limit error. I played with it and it appears to come after I printed a fixed number of text to R via Rprintf (not from the main thread). Didn't happen on the old machine. Old version was 2.14. Now on 3.0.3. Not sure whats going on. Florian [[alternative HTML

I get this error on one computer running Fedora Core 5 but not on another one, when I start R from Xemacs using ESS. After I get the error with Xemacs, I get it even without using Xemacs. I haven't tried all possibilities, because I have found discussion of this problem on the R-devel mailing list, so clearly some people understand it. (Not me.) I'm posting here in case someone has a

Hi everyone! I meet one problem when embedding R in C code, when I run the the R code in one child thread , it always print error info: Error: C stack usage is too close to the limit I also try to set R_CStackLimit = (uintptr_t)-1 to disable the C stack check as the R-ext doc say, but it still does not work. it is interesting that if i put the R code in the main

Apparently the way to deal with this error message is to set R_CStackLimit = (uintptr_t)-1 I tried typing this in the R console, but it says Error: object "R_CStackLimit" not found. So where do I type it? In one of the initialization files that R uses when it starts up? I can't find the answer anywhere. Please note that I don't understand words like "DLL" or

Hi everyone! I meet one problem when embedding R in C code, when I run the the R code in one child thread , it always print error info: Error: C stack usage is too close to the limit I also try to set R_CStackLimit = (uintptr_t)-1 to disable the C stack check as the R-ext doc say, but it still does not work. it is interesting that if i put the R code in the main

Hi, I encountered an error of type 'C stack usage is too close to the limit', and could not find information so far to get unstuck. The error occurs when subsetting columns from a data frame (see stack trace below). However if I step through the sequence of code found in the 'topmost' function buildCombinations the data processing is successful. I get an identical behavior on

Hi, I would appreciate if someone could comment on this problem I am experiencing. I am writing a C++ program to be called from R. In this program, there is a verbose switch that decides whether to print some debugging info using Rprintf. On windows, things work ok. On linux, things are fine in non-verbose mode, but in verbose mode, I get error saying "C stack usage is too close to the

R-help, I 'm trying to optimize a model to data using log-likelihoods but I encounter the following error message: > l= c(49.4, 57.7,64.8,70.9,78.7,86.6,88.3,91.6,99,115) > t=3:12 > fn <- function(params, l=l, t=t) { Linf <- params[1] k <- params[2] t0 <- params[3] sigma <- params[4]

I am trying to set up a RApache server on my Ubuntu 8.04. I have installed apache2, R-2.7.0, and the RApache plugin. Both Apache and R seem to work fine, but whenever i try to use the plugin i get this error: C stack usage is too close to the limit. I have tried to recompile apache2, R, and RApache, but i keep getting the error. The weird thing is, i had exactly the same problem when i installed

Lately R has been behaving strange on my Linux (Ubuntu 7.10) machine, with occasional segfaults. Today something else and reproducible happened: If I type the code below (meant for calibrating data), I get the error message that "the C stack usage is too close to the limit". calcurve <- cbind(1:2e4, 1:2e4, 1:2e3); #dummy curve, real one is more complex caldist <-

Hi everyone! I meet one problem when embedding R in C code, when I run the the R code in one child thread , it always print error info: Error: C stack usage is too close to the limit I also try to set R_CStackLimit = (uintptr_t)-1 to disable the C stack check as the R-exts doc say, but it still does not work, the error info still exist. Besides it is interesting that if i

R-helpers: I'm running a file search on my entire drive (Mac OS X) using: files_found <- list.files(dir="/",pattern=somepattern,recursive=TRUE,full.names=TRUE) where somepattern is a search pattern (which I have confirmed via a unix "find / -name somepattern" only returns ~ 3 results). I keep getting an error: Error: C stack usage is too close to the limit when

Hello all, I came across<http://www.r-bloggers.com/performance-benefits-of-linking-r-to-multithreaded-math-libraries/> David Smith's new post Performance benefits of linking R to multithreaded math libraries<http://blog.revolutionanalytics.com/2010/06/performance-benefits-of-multithreaded-r.html> Which explains how (and why) REvolution distribution of R uses different BLAS math

The current VC6 project file is set to use the single-threaded C library in Windows. This causes crashed when it hits the (temporary) fprintf's in the library. Since using multithreaded libraries in a single threaded program does no harm and will do away with these crashes in multithreaded programs, I suggest that the VC6 file should be changed to use the multi-threaded libs. I'm not a

On May 23, 2009, at 9:41 PM, Xi Wang wrote: > There is no __sync_synchronize or __sync_val_compare_and_swap on Mac > OS X. One might use OSMemoryBarrier or OSAtomicCompareAndSwap32 > instead. The patch is attached. Actually, __sync_synchronize and __sync_val_compare_and_swap DO exist on Darwin, but only if you use Apple's GCC 4.2 (or later), just as it is on Linux. We always

Dear R developers, We have a big SGI Origin computation server with 32 cpu's and 64 Gb of RAM. In R 2.0.0 we could run large jobs, allocating 8 Gb of RAM was not a problem, for example by running: > v1 <- seq(1,2^29) > v2 <- seq(1,2^29) > v3 <- seq(1,2^29) > v4 <- seq(1,2^29) This yields an R process, consuming about 8 Gb of RAM: PID PGRP USERNAME

Move get_rx_bufs() to vhost.c and rename it to vhost_get_bufs(). This helps to hide vring internal layout from specific device implementation. Packed ring implementation will benefit from this. Signed-off-by: Jason Wang <jasowang at redhat.com> --- drivers/vhost/net.c | 77 -------------------------------------------------- drivers/vhost/vhost.c | 78

Move get_rx_bufs() to vhost.c and rename it to vhost_get_rx_bufs(). This helps to hide vring internal layout from specific device implementation. Packed ring implementation will benefit from this. Signed-off-by: Jason Wang <jasowang at redhat.com> --- drivers/vhost/net.c | 83 ++------------------------------------------------- drivers/vhost/vhost.c | 78

Hi, all, I just recently noticed a change in terms.formula from 2.2.1 to 2.3.1 (possibly 2.3.0, but I didn't check). Here's the problem: ## 2.2.1 > update(~ x | y, z ~ .) z ~ x | y ## 2.3.1 > update(~ x | y, z ~ .) z ~ (x | y) and in the NEWS for 2.3.1 o terms.formula needed to add parentheses to formulae with terms containing '|'. (PR#8462) So, there must be

Thanks. I think I am using Apple GCC 4.2. i686-apple-darwin9-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5566) Should I use something else for LLVM? - xi On Sun, May 24, 2009 at 1:20 AM, Owen Anderson <resistor at mac.com> wrote: > > On May 23, 2009, at 9:41 PM, Xi Wang wrote: > > There is no __sync_synchronize or __sync_val_compare_and_swap on Mac > OS X.  One might use