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

Mapping vtable addresses to Rust type #35

Open
tyt2y3 opened this issue Jan 8, 2024 · 0 comments
Open

Mapping vtable addresses to Rust type #35

tyt2y3 opened this issue Jan 8, 2024 · 0 comments

Comments

@tyt2y3
Copy link
Member

tyt2y3 commented Jan 8, 2024

Would love to have some ideas on the best way to map vtable addresses back to the original Rust types.

Say we have a Box<dyn MyTrait>, the goal is to lookup the original type info from the vtable address, and then use the type info to decode the data at the data address.

We can already do this for normal boxed types, because we trace allocations. Since there is no allocation for Zero Sized Types, this trick does not work.

Originally posted by @tyt2y3 in #34

@tyt2y3 tyt2y3 changed the title Would love to have some ideas on the best way to map vtable addresses back to the original Rust type. Mapping vtable addresses to Rust type Jan 8, 2024
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