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
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.
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
The text was updated successfully, but these errors were encountered: