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
Currently my Dr. Memory prototype only supports byte-level shadowing.
That matches Purify, and I originally thought it would be sufficient
to avoid false positive and would only be desirable for avoiding
rare false negatives for apps using bitfields.
However, "hello world" compiled with cygwin g++ has 3 false positives
due to bitfields, and I suspect linux gcc has some (PR 408123).
Avoiding false positives makes this higher priority than avoiding
false negatives.
I do have a tag for "special" in the shadow memory table that is meant
for per-bit shadowing (as well as retaddr: PR 406731), but my shadow
registers do not support per-bit. Should be easy to add on Linux,
but on Windows my all-TLS scheme could have transparency issues with
some large apps that take many TLS slots. May want to switch to
a stolen base register.
PR 488813 is one test case
*** Bug 585742 has been marked as a duplicate of this bug. ***
Not planning to support for MN
Based on DEV and QA agreement, there is no QA resource allocated for MN UW and UW tools.
Accepted all MN deferred bugs. Please feel free to change it back. Thanks.
From derek.br...@gmail.com on December 10, 2010 17:57:42
PR 408523
Currently my Dr. Memory prototype only supports byte-level shadowing.
That matches Purify, and I originally thought it would be sufficient
to avoid false positive and would only be desirable for avoiding
rare false negatives for apps using bitfields.
However, "hello world" compiled with cygwin g++ has 3 false positives
due to bitfields, and I suspect linux gcc has some (PR 408123).
Avoiding false positives makes this higher priority than avoiding
false negatives.
I do have a tag for "special" in the shadow memory table that is meant
for per-bit shadowing (as well as retaddr: PR 406731), but my shadow
registers do not support per-bit. Should be easy to add on Linux,
but on Windows my all-TLS scheme could have transparency issues with
some large apps that take many TLS slots. May want to switch to
a stolen base register.
PR 488813 is one test case
*** Bug 585742 has been marked as a duplicate of this bug. ***
Not planning to support for MN
Based on DEV and QA agreement, there is no QA resource allocated for MN UW and UW tools.
Accepted all MN deferred bugs. Please feel free to change it back. Thanks.
Original issue: http://code.google.com/p/drmemory/issues/detail?id=113
The text was updated successfully, but these errors were encountered: