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

Determine if we need to do something re: nonmoveable structures #1905

Open
riverar opened this issue May 10, 2024 · 0 comments
Open

Determine if we need to do something re: nonmoveable structures #1905

riverar opened this issue May 10, 2024 · 0 comments

Comments

@riverar
Copy link
Collaborator

riverar commented May 10, 2024

Pulled out of #1821 so we don't lose it.

CREDENTIALW is an interesting related case. It isn't empty in the metadata, nor should it be. But CredReadW returns a PCREDENTIALW that is important to not copy around. The original pointer is native allocated memory that must be freed via the original pointer. Further, the struct may point to addresses outside itself but within the same memory allocation. So it's important that projections not simply copy the struct and/or release the memory and expect the copy to be self-contained.
I think these fall in with the native classes mentioned in the description, in that the metadata should be able to indicate that this type should never be dereferenced for purposes of copying around, as the original pointer is important.

Originally posted by @AArnott in #1821 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant