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
Update shadow memory tracking to be allocation-based rather than the old fragment-based system (recreated memory was updated way back in 97b8557).
Implement methods to retrieve/set the shadow state of memory that can be used by instrumented code and interceptors.
Update the instrumentation to propagate uninitialized bits through instructions.
In the long term, it would be nice to have a large block of shadow memory so that determining the location of the shadow memory for any particular byte was a simple operation (a la Memcheck, MemorySanitizer, etc.)
The text was updated successfully, but these errors were encountered:
This is in preparation for bit-level initialization tracking
(mheinsen issue #9). This also simplifies the tracking of
initialization within allocations, though we do have to ensure
that allocations are added and removed correctly (and we never
try to set or clear the initialization of memory if the
allocation does not exist).
Note that this brings the tracing system's handling into line
with the replay system, which became allocation-based back in
commit 97b8557 !
I think that this should proceed as follows:
In the long term, it would be nice to have a large block of shadow memory so that determining the location of the shadow memory for any particular byte was a simple operation (a la Memcheck, MemorySanitizer, etc.)
The text was updated successfully, but these errors were encountered: