Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CRAN san checking issue on generated code on Windows only #1524

Open
perrydv opened this issue Jan 7, 2025 · 0 comments
Open

CRAN san checking issue on generated code on Windows only #1524

perrydv opened this issue Jan 7, 2025 · 0 comments
Labels

Comments

@perrydv
Copy link
Contributor

perrydv commented Jan 7, 2025

We have a report that the nimbleFunction line

xPrev     = nimNumeric(length=lengthOri, value=x[1:lengthOri])

where x is an argument, and the compileNimble call is in a package vignette, gives the following error on Windows only:

File: build_vignettes.log
/home/hornik/tmp/CRAN_special_gcc-san/Library/nimble/include/nimble/nimbleEigenNimArr.h:244:11: runtime error: null pointer passed as argument 1, which is declared to never be null
/home/hornik/tmp/CRAN_special_gcc-san/Library/nimble/include/nimble/nimbleEigenNimArr.h:244:11: runtime error: null pointer passed as argument 2, which is declared to never be null

It doesn't appear that those arguments should be null pointers. I suggested the user work around the error by the more direct

xPrev = x[1:lengthOri]

but nevertheless I want to record this for future reference and possible clean-up.

@perrydv perrydv added the cleanup label Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant