similar to: capturing value of C or Fortran function

(Sorry for the cross-post--- I wasn't sure which list is more appropriate...) Hi everyone, I've run into segfaults when using my randomForest package on large dataset (e.g., 100 x 15200) and large number of trees (e.g., ntree=7000 and mtry=3000). I'm wondering if anyone can give me some hints on where to look for the problem. The randomForest package mainly consists of two things:

(Sorry for the cross-post--- I wasn't sure which list is more appropriate...) Hi everyone, I've run into segfaults when using my randomForest package on large dataset (e.g., 100 x 15200) and large number of trees (e.g., ntree=7000 and mtry=3000). I'm wondering if anyone can give me some hints on where to look for the problem. The randomForest package mainly consists of two things:

Dear R-devel, Last week I got several responses to my question about debugging segfaults in my code (original post below). After I changed the S_alloc() calls to Calloc()/Free(), the symptom was gone, but I was told to keep looking. So I did: o Switched to Calloc/Free. Electric Fence did not find any problem. o Put assert(index < bound); assert(index >=0); everywhere in the C routine

Hi all, I've just been working with a piece of fortran code (Leo Breiman's random forest code) that needs a lot of arguments. When I use .Fortran, I get the message 'too many arguments in foreign function call'. Neither the help page for .Fortran (actually Foreign) nor "Writing R Extensions" explains how many arguments are too many. Looking at the code in

Hi all, I've just been working with a piece of fortran code (Leo Breiman's random forest code) that needs a lot of arguments. When I use .Fortran, I get the message 'too many arguments in foreign function call'. Neither the help page for .Fortran (actually Foreign) nor "Writing R Extensions" explains how many arguments are too many. Looking at the code in

Hi, I am segfaulting when using predict.loess() (checked with r62092). I've traced the source with the help of valgrind (output pasted below) and it appears that this is due to int overflow when allocating an int work array in loess_workspace(): liv = 50 + ((int)pow((double)2, (double)D) + 4) * nvmax + 2 * N; where liv is an (global) int. For D=1 (one x variable), this overflows at

supsmu(periodic=TRUE) can crash R by reading before start of array. To reproduce: set.seed(1) xx <- runif(29000) yy <- rnorm(29000) span <- 0.49 i <- 1 while(i < 200){ cat(i,"\n") int <- supsmu(xx,yy,periodic=T,span=span) i <-i+1 } results in: 1 2 3 4 5 6 7 8 9 Program received signal SIGSEGV,

Why doesn't R have one, like "." in Perl or juxtaposition in awk? It does not seem impossible to introduce one, if that would be reasonable. It would seem to involve adding a table entry to main/names.c for the binary operator and a corresponding internal function, say do_dot(). This cannot be simply do_paste(), since the implied separator is "". So, do_dot() might be

We are having problems building R on Red Hat Linux 6.0/Sparc. R compiles with no problem but then it fails "make tests". Specifically, the line eigen(cbind(-1,c(1:2,0),0:2)) # complex values causes a segmentation fault. Previous versions of Red Hat Linux did not give this problem. The eigen() function is one of the rare cases in the base library where Fortran code is called via the

Hi, [System info: R 1.6.1 compiled from source (no args to configure) on Redhat 7.1 Linux i/386] I have some spatial statistics programs that recently (since R 1.6.1) have generated SIGSEGV. These R programs use the splancs library as well as some C code of my own for Voronoi analysis. The program has a big loop to fit various model parameters against a spatial distribution of biological

Hi all, I'm preparing a package which uses .Fortran to interface a Fortran 95 function. This F95 function simply receives the name of a file from R, opens this file and forwards its content to a F95 module, which, in turn, makes the real computation. The F95 module is a pre-existing one and I'm trying to use it in its actual state. Thus, data transfer between R and this F95 module is

I have an ASAN enabled version of R-devel on my test machine, and can get it to relably crash.? Here is the first part of the session: tmt-local2434% R --vanilla R Under development (unstable) (2019-06-28 r76752) -- "Unsuffered Consequences" Platform: x86_64-pc-linux-gnu (64-bit) R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to redistribute it under

This might more properly be filed as a bug report, but ... I came upon the following problem while trying to dyn.load a library of Fortran code into R. I'm running RedHat 7.1 on a Pentium III laptop, with R version 1.3.1 (latest rpm from CRAN) and gcc/g77 version 2.96. My library has a number of Fortran subroutines that have underscores in their names for readability. By default g77

dear wizards: FYI: gentoo is a linux meta distribution, which compiles all packages. Once running, gentoo is stable on most applications. (it has some problems with system tools, such as grub.) the compiler is gcc 3.3.3. I do not expect anyone to track down for me why R fails on the gentoo amd64+gcc3.3.3 system, but I thought that it would be good to put it on the record to save

dear wizards: FYI: gentoo is a linux meta distribution, which compiles all packages. Once running, gentoo is stable on most applications. (it has some problems with system tools, such as grub.) the compiler is gcc 3.3.3. I do not expect anyone to track down for me why R fails on the gentoo amd64+gcc3.3.3 system, but I thought that it would be good to put it on the record to save

Hi, Could someone please point to an example of passing strings from .C() calls back to R? I want to be able to do something like this: str <- .C("return_foo_string", str=character(1))$str void return_foo_string(char ** str) { *str = "foo"; } The above code has at least two memory allocation "concerns": 1) How to properly allocate "foo". I

OK, to summarize and clarify a bit 1) I downloaded some code that existed in "pure" FORTRAN, FORTRAN+S-Plus, and FORTRAN+R versions. 2) I discovered that the primary difference between R and S-Plus version was the use of a wrapper to reduce the number of arguments from 87 to 65. When I inquired why, the author of the code replied "R won't take more than 65 arguments to

Full_Name: Benjamin Tyner Version: 2.1.0, 4/18/2005 OS: i686-redhat-linux-gnu Submission from: (NULL) (4.64.8.220) # Just run my.test() below in a newly opened R session. Once too many models have been fit (~20 on my system), the computed standard error jumps to a different value. This is (superficially) due to a different residual sum of squares, not a different one.delta. No other aspect of

Dear R-devel, While tracking down some hard-to-reproduce bugs in a package I maintain, I stumbled on a behavior change between R 2.15.0 and the current R-devel (or SVN trunk). In 2.15.0 and earlier, if you passed an 0-length vector of the right mode (e.g., double(0) or integer(0)) as one of the arguments in a .C() call with DUP=TRUE (the default), the C routine would be passed NULL (the C

Dear list-members, I have observed quite a strange problem with the date package. You will find below what I get on my machine (Ubuntu). I have been able to reproduce the error on Red Hat too. But it seems not to happen on Windows (and on some other Linux distros?). > require(date) Loading required package: date > sessionInfo() R version 2.15.2 (2012-10-26) Platform: x86_64-pc-linux-gnu