Agreed on divide-and-conquer. There is no other way. Valgridn et al may move some code to registers for subtle changes.
On 4 July 2015 at 10:20, Charles Geyer wrote: | I should add a more direct question. When a crash occurs ONLY when running R | CMD check, how does one debug that? Usually one would say that R CMD check | --use-valgrind | is the answer. But it only segfaults when --use-vagrind is not used. So | somehow we have to debug R CMD check itself. How? By "mocking" the exact same (compile and run-time) options used by R CMD check. You can trace that down. Things depend a little on whether you do or do not use user-library-paths for .libPaths() or not, whether you use per-user compile flags etc pp. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
