The general prescription is: 1. Try running the code with `gctortue(TRUE)` on, 2. Try running with a debugger (gdb, lldb, valgrind), 3. Try running with sanitizers (see e.g. Dirk's docker containers: https://github.com/eddelbuettel/docker-ubuntu-r)
This should help provide you (and/or us) enough information to diagnose the problem. Cheers, Kevin On Wed, Aug 20, 2014 at 10:38 AM, Gregor Kastner <gregor.kast...@wu.ac.at> wrote: > Dear all, > > during a large simulation study on around 300 cores, I have just noticed > "strange" behavior of my package depending on Rcpp. "Strange" in the sense > that on very rare occasions (around 1 in 100000 function calls > through .Call), a NumericMatrix object created at C level and returned back > to R as part of a list isn't available there, causing a "memory not mapped" > segfault when trying to access it from R. The issue is not > deterministically > reproducible and, as mentioned, very rare. This makes narrowing down the > bug > a pain. I do know however that this problem does not appear in Rcpp 0.10.5 > but does appear in Rcpp 0.11.0. Maybe there is anyone out there who has > experienced something similar or otherwise has a hunch where I should dig > further. > > Thanks a ton in advance, > Gregor > _______________________________________________ > Rcpp-devel mailing list > Rcpp-devel@lists.r-forge.r-project.org > https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel >
_______________________________________________ Rcpp-devel mailing list Rcpp-devel@lists.r-forge.r-project.org https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel