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
Remove padding bytes risk in dbghelp with MaybeUninit
As reported in #720, there is a risk that the
current code, by using &mut to a struct with padding fields,
interacts in ways that cause padding bytes to be written to bytes
that Rust originally thought were real and initialized.
If this assumption persists forward in time far enough,
this could possibly cause an issue due to compiler optimizations.
This seems unlikely, but we can fix this by using MaybeUninit and then
addressing the data using raw pointers only. That way, we do not have
to depend on all the data being in initialized states even after calling
SymFromAddrW. Except for the specific fields we read, of course.
0 commit comments