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

Support bit-level initialization tracking. #9

Closed
mheinsen opened this issue Mar 15, 2013 · 1 comment
Closed

Support bit-level initialization tracking. #9

mheinsen opened this issue Mar 15, 2013 · 1 comment
Assignees

Comments

@mheinsen
Copy link
Owner

I think that this should proceed as follows:

  1. Update shadow memory tracking to be allocation-based rather than the old fragment-based system (recreated memory was updated way back in 97b8557).
  2. Implement methods to retrieve/set the shadow state of memory that can be used by instrumented code and interceptors.
  3. 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.)

@ghost ghost assigned mheinsen May 28, 2013
mheinsen added a commit that referenced this issue Aug 8, 2016
mheinsen added a commit that referenced this issue Sep 11, 2016
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 !
@mheinsen
Copy link
Owner Author

mheinsen commented Dec 1, 2016

This issue was moved to seec-team#16

@mheinsen mheinsen closed this as completed Dec 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant