-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Memory address error with RDsan #14
Comments
I don't think this has anything to do with OE> ==101==Shadow memory range interleaves with an existing memory mapping. ASan cannot proceed correctly. ABORTING.
OE> ==101==ASan shadow was supposed to be located in the [0x00007fff7000-0x10007fff7fff] range.
OE> ==101==This might be related to ELF_ET_DYN_BASE change in Linux 4.12.
OE> ==101==See https://github.com/google/sanitizers/issues/856 for possible workarounds. More details here: https://bbs.archlinux.org/viewtopic.php?id=228947 I'm not seeing any issue on the CRAN check side that RDscan would pick up: https://cran.r-project.org/web/checks/check_flavors.html#r-devel-windows-x86_64-new-TK Perhaps open the ticket with Winston? |
Thanks for looking at it. I added a ping to Winston. |
Going to close out this issue as it's been over a year and the issue was filed upstream. |
I'm trying to test a different package with RDsan, and I get the following error. Unfortunately, I don't know enough about the C side of things to provide much more information.
To replicate it, I put the following into a Dockerfile and ran
docker build -t sitmo-rdsan .
.Dockerfile:
Error:
The text was updated successfully, but these errors were encountered: