You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would love to have some ideas on the best way to map vtable addresses back to the original Rust type.
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.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Would love to have some ideas on the best way to map vtable addresses back to the original Rust type.
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.
Beta Was this translation helpful? Give feedback.
All reactions