Initialize variables for MSAN

The variables in the CL are not initialized. Even if it's safe not to
initialize them here, MSAN doesn't know that.

Bug: 394028
Change-Id: I597a7d76aa19d5789decd0f85150fa31c9655269
Reviewed-on: https://chromium-review.googlesource.com/1001573
Reviewed-by: Lei Zhang <thestig@chromium.org>
This commit is contained in:
Sergey Abbakumov 2018-04-10 10:09:44 +07:00 committed by Lei Zhang
parent adcc90ddb8
commit c83fcf6470
2 changed files with 2 additions and 2 deletions

View file

@ -549,7 +549,7 @@ bool ExceptionHandler::GenerateDump(CrashContext *context) {
// Allow the child to ptrace us // Allow the child to ptrace us
sys_prctl(PR_SET_PTRACER, child, 0, 0, 0); sys_prctl(PR_SET_PTRACER, child, 0, 0, 0);
SendContinueSignalToChild(); SendContinueSignalToChild();
int status; int status = 0;
const int r = HANDLE_EINTR(sys_waitpid(child, &status, __WALL)); const int r = HANDLE_EINTR(sys_waitpid(child, &status, __WALL));
sys_close(fdes[1]); sys_close(fdes[1]);

View file

@ -262,7 +262,7 @@ class ExceptionHandler {
// can do this. We create a pipe which we can use to block the // can do this. We create a pipe which we can use to block the
// cloned process after creating it, until we have explicitly enabled // cloned process after creating it, until we have explicitly enabled
// ptrace. This is used to store the file descriptors for the pipe // ptrace. This is used to store the file descriptors for the pipe
int fdes[2]; int fdes[2] = {-1, -1};
// Callers can add extra info about mappings for cases where the // Callers can add extra info about mappings for cases where the
// dumper code cannot extract enough information from /proc/<pid>/maps. // dumper code cannot extract enough information from /proc/<pid>/maps.