This tweet constitutes my bi-annual "Thank You!" 🙏 to @winston_chang for his sumo-style container which once again let me chase and pinpoint an ASAN/clang issue my own ASAN/gcc container did not tickle. Also, CRAN is awesome in its rigour. #rstats github.com/wch/r-debug

GitHub - wch/r-debug: Dockerfile with several builds of R for memory/thread debugging

Dockerfile with several builds of R for memory/thread debugging - GitHub - wch/r-debug: Dockerfile with several builds of R for memory/thread debugging

github.com
1
4
23
Glad it can be of help! It is in need a bit of maintenance to keep it up to date, though…
1
Replying to @winston_chang
The biggest issues are toolchain changes, as well as following updates to the spec used 'at that other site we all follow'. I had started with a pair for clang and gcc and at some point last year the clang one stopped building. So yeppers, maintenance ahead ...

Jul 16, 2023 · 10:44 PM UTC

1
Replying to @eddelbuettel @winston_chang
These have been incredibly useful when I have to track down bugs that the CRAN team have identified. I use the ASAN/UBSAN containers to check xts before every release. Thanks Winston!