There's also R Hub by Gábor Csárdi: https://builder.r-hub.io/advanced
It provides a win-builder-like service where you can test your package with different R setups, including 'Debian Linux, R-devel, GCC ASAN/UBSAN'. There's also an 'rhub' package that allows you to run all this from the R prompt. It's simply great. /Henrik On Wed, Nov 6, 2019 at 12:41 PM Ivan Krylov <krylov.r...@gmail.com> wrote: > > On Wed, 6 Nov 2019 08:43:50 -0600 > Marcin Jurek <marcinjurek1...@gmail.com> wrote: > > > I have very little clue what to do, above all because I don't know > > how to reproduce the error. > > Using AddressSanitizer to find memory errors in R packages requires the > R installation to be built with AddressSanitizer, too. > > I found it useful to build the package with -g (and maybe -Og), then > run the checks using `R -d valgrind CMD check ...`. Sometimes the > errors found by Valgrind are different from errors found by > AddressSanitizer, though (not to mention the differences in hardware). > > -- > Best regards, > Ivan > > ______________________________________________ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
