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

Performance: Avoid taking stacks in the presence of whole-module suppressions #839

Closed
derekbruening opened this issue Nov 28, 2014 · 1 comment

Comments

@derekbruening
Copy link
Contributor

From [email protected] on March 20, 2012 14:13:17

See issue #412 and issue #792 .

From a comment in 792:

The suppression we're using for issue #412 covers all uninits in rsaenh.dll. I spent a week trying to figure that out and didn't get anywhere, so I suppressed it and moved on. We could try to fix it properly, but for now it would help just to avoid taking those stack traces and symbolizing them. If we detect a module level suppression for a given error type, we could short-circuit our reporting before we take the stack trace. This should be good enough, and would be easier than trying to change our instru to propagate definedness bits without generating uninit reports.

This issue covers implementing that.

Original issue: http://code.google.com/p/drmemory/issues/detail?id=839

@derekbruening
Copy link
Contributor Author

From [email protected] on March 20, 2012 11:16:16

Status: Duplicate
Mergedinto: 838

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