-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
MemorySanitizer: use-of-uninitialized-value issue due to accessing destroyed class member #20913
MemorySanitizer: use-of-uninitialized-value issue due to accessing destroyed class member #20913
Conversation
…emorySanitizer: use-of-uninitialized-value issue. Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
For reviewers: ==7987==WARNING: MemorySanitizer: use-of-uninitialized-value Memory was marked as uninitialized ==7987==WARNING: MemorySanitizer: use-of-uninitialized-value
#0 in Envoy::AccessLog::AccessLogFileImpl::doWrite(Envoy::Buffer::Instance&) source/common/access_log/access_log_manager_impl.cc #15 in Envoy::Server::AdminImpl::~AdminImpl() source/server/admin/admin.h:64:7 #18 in Envoy::Server::InstanceImpl::~InstanceImpl() source/server/server.cc:163:1 Memory was marked as uninitialized The fix is just to reorder members. |
/assign @vitalybuka @wbpcode |
@vitalybuka cannot be assigned to this issue. |
LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks cc @vitalybuka @yanjunxiang-google
…emorySanitizer: use-of-uninitialized-value issue. (envoyproxy#20913) Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
Accessing destroyed class member causing MemorySanitizer: use-of-uninitialized-value issue
Signed-off-by: Yanjun Xiang yanjunxiang@google.com
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]