Re: [R-pkg-devel] Package valgrind problem I can't solve: Direction?

2017-11-06 0:09 GMT+01:00 Peter Dunn : > Impossible or not… it just happened (unless I am being really stupid, which > is entirely possible, indeed probable). I confirmed again this morning: > After rebuilding (R CMD build) and checking (R CMD check) without any > errors, I used

Re: [R-pkg-devel] Package valgrind problem I can't solve: Direction?

“unless I am being really stupid” Lucky for that caveat. Feeling rather stupid for this late effort. Thanks so much. Help greatly appreciated. P. On 6/Nov/17, 9:51 am, "Iñaki Úcar" wrote: 2017-11-06 0:09 GMT+01:00 Peter Dunn : > Impossible or

Re: [R-pkg-devel] Package valgrind problem I can't solve: Direction?

Impossible or not… it just happened (unless I am being really stupid, which is entirely possible, indeed probable). I confirmed again this morning: After rebuilding (R CMD build) and checking (R CMD check) without any errors, I used rhub and the command line again: Running valgrind at the

Re: [R-pkg-devel] Package valgrind problem I can't solve: Direction?

Peter, I ran into similar problems with using valgrind to check my package BAS From my understanding using valgrind with rhub does not run the same checks as R -d "valgrind --tool=memcheck --leak-check=full" --vanilla < mypkg-Ex.R see https://github.com/r-hub/rhub/issues/23 which might