-
Notifications
You must be signed in to change notification settings - Fork 144
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
Fix pin prob #855
Fix pin prob #855
Conversation
I think it's still broken the same way it was before @adetaylor . Rust is moving storage without calling a C++ copy or move constructor again. It's interesting that it passes asan, maybe the compiler optimizes the memory allocation out completely? https://github.com/google/autocxx/runs/5391090192?check_suite_focus=true shows it failing even though I'm pretty sure my changes in #843 don't cause it. On top of current main, this patch:
makes it fail for me locally, and print this when it does fail:
|
I don't see the crash, but I do see that one of the destructor addresses doesn't match up, so looking now. |
Pretty sure this is it - what do you think, @bsilver8192? #872 |
Yep, I think that fixes it. |
Fixes #833 by documenting all unsafe code, and forbidding unsafe code in most places.