On 9/29/25 19:14, quirin stier wrote:
I submitted a locally functioning package to CRAN (see https://github.com/Quirinms/GeneralizedUmatrixGPU), however in the case of the Linux test, I get following error: *** caught segfault *** address 0x10, cause 'memory not mapped'
Just from these two lines, one can't tell what was the problem. It would be slightly better to see complete outputs of the failed checks, that could give a hint where it failed.
To provoke the crash on a system where it normally doesn't happen, one might try using gc torture (see ?gctorture). Also one might try running with address sanitizer/valgrind to see if those tools could find a memory error. Possibly one could run only a smaller part of the check, based on the output - e.g. if it crashes while running a specific example, one might try just running that example in isolation (with gctorture, valgrind, etc).
Certainly that it crashes on some platforms means there is an error (in the package, or depenendent packages, or possibly used libraries or R).
Best Tomas
A web search suggests that the executing machine must have a "mismatch between currently installed shared libraries and the libraries that were built to install R or packages". https://stackoverflow.com/questions/49190251/caught-segfault-memory-not-mapped-error-in-r [[alternative HTML version deleted]] ______________________________________________ [email protected] mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
______________________________________________ [email protected] mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
