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

Displaying 20 results from an estimated 20000 matches similar to: "Error: C stack usage is too close to the limit"

2008 Jun 12
1
Rprintf and "C stack usage is too close to the limit"
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
2009 May 21
1
"Error: C stack usage is too close to the limit" (can't understand explanations of how to fix this)
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
2009 May 19
2
About " Error: C stack usage is too close to the limit"
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
2009 May 18
0
About " Error: C stack usage is too close to the limit"
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
2009 May 19
0
About " Error: C stack usage is too close to the limit"--resend
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
2007 Jun 01
3
Question on the R's C stack limit
Dear r-devel members, I encountered a C stack limit issue, when I tried to embed R 2.5 into my application. In the R-exts document, it says:"Note that R's own front ends use a stack size of 10Mb". I desire to know: is it possible to decrease this stack size by modifying R's source code? If it's possible, which part of the source code is responsible for the issue? Thank
2010 Apr 30
1
X11() device widht and height parameters limited to one screen
Hi, if I specify the width and height of a plot I want to see via > X11(width=14,height=7) > X11(width=28,height=14) > X11(width=20,height=14) > X11(width=13,height=14) > X11(width=15,height=14) any width greater than 15 is ignored as it seems the width is limited by the screen width. However, as I am using two screens (xinerama), I can easily manually resize to fit two
2011 Feb 04
3
Apply parameters to a function from a list
Hey, this may be a simple question, but I am struggling to apply a list of parameters to a function. Say I have the following function: test<-function(a=1,b=2,c=3,d=4){a+b+c+d} And the following list: point<-list(a=3,d=2) Is there a way I can evaluate function test at point? (Apart from changing function test to take in a list, and take values out of the list, but I'd rather
2006 Jun 26
0
C stack usage is too close to the limit
I am getting a seg fault and the following error when trying to use an embedded version of R in a multithreaded application. Error: C stack usage is too close to the limit When I do the same thing in a single threaded app, then there is no problem. I've tried this with R version 2.3.0, 2.3.1 and even 2.2.1 and the same error occurs. Any tips on how to solve this would be greatly
2006 Apr 27
1
Error: C stack usage is too close to the limit
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
2008 Dec 19
1
'Error: C stack usage is too close to the limit' when adding an overarching function
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
2009 Sep 14
1
Error: C stack usage is too close to the limit
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]
2008 May 27
1
error: C stack usage is too close to the limit.
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
2008 Jan 26
2
Error: C stack usage is too close to the limit
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 <-
2007 Feb 07
3
Redirect --stats to STDERR.
Hello, I have written a little script that's would email me all errors. rsync -vah --delete --stats <sources> <destination> > /var/log/sauvegarde/listoffile.log 2> /var/log/sauvegarde/errors.log My problem is i want to have the stats in my mail. Is it possible to redirect --stats to STDERR. I have tryed to do this : /---
2007 Jul 06
1
How to disable R's C stack checking
Hi all, I'm developing an application on Mac OS X Darwin which embeds R. However, the application always crashes due to the C stack checking. I know that R_CStackLimit can be set to -1 to disable the stack checking, but I don't know where to put the code "R_CStackLimit=-1". Please give some instructions. Thank you very much! Here is my compiler infomation: $g++ -v Using
2004 Jan 27
1
Differentiating debug messages from both sides
Some of the debug messages that rsync outputs (when verbose >= 2) can occur on both sides of the connection. This makes it hard to know which program is saying what. Some debug messages deal with this by outputting a "[PID]" string at the start of the message. Unfortunately, the startup message that tells us which pid is which is only output when verbose >= 3, so there's a
2009 Jun 12
1
Can't get F77_CALL(dgemm) to work [SEC=UNCLASSIFIED]
Hi I am new to writing C code and am trying to write an R extension in C. I have hit a wall with F77_CALL(dgemm) in that it produces wrong results. The code below is a simplified example that multiplies the matrices Ab and Bm to give Cm. The results below show clearly that Cm is wrong. Am= 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Bm= 1 1 1 1 1
2002 Aug 05
5
[patch] read-devices
Greetings, I'd like to propose a new option to rsync, which causes it to read device files as if they were regular files. This includes pipes, character devices and block devices (I'm not sure about sockets). The main motivation is cases where you need to synchronize a large amount of data that is not available as regular files, as in the following scenarios: * Keep a copy of a block
2002 May 04
1
A simpler move-files patch
In an effort to get my long-desired move-files functionality into rsync, I have created a version of my patch that runs as an extra pass at the end of the processing. This results in a simpler set of changes to rsync. I still think it would be nice to have incremental deletions during large transfers (as my first patch provides), but acceptance of this patch would relegate such quibbling to a