2015-05-28 09:04:17 -07:00
|
|
|
// Copyright 2015 The Crashpad Authors. All rights reserved.
|
|
|
|
//
|
|
|
|
// Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
// you may not use this file except in compliance with the License.
|
|
|
|
// You may obtain a copy of the License at
|
|
|
|
//
|
|
|
|
// http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
//
|
|
|
|
// Unless required by applicable law or agreed to in writing, software
|
|
|
|
// distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
// See the License for the specific language governing permissions and
|
|
|
|
// limitations under the License.
|
|
|
|
|
|
|
|
#ifndef CRASHPAD_TEST_WIN_WIN_MULTIPROCESS_H_
|
|
|
|
#define CRASHPAD_TEST_WIN_WIN_MULTIPROCESS_H_
|
|
|
|
|
|
|
|
#include <windows.h>
|
|
|
|
|
2016-01-06 12:22:50 -05:00
|
|
|
#include "base/macros.h"
|
2015-07-31 12:31:58 -04:00
|
|
|
#include "gtest/gtest.h"
|
|
|
|
#include "test/win/win_child_process.h"
|
2015-05-28 09:04:17 -07:00
|
|
|
#include "util/file/file_io.h"
|
|
|
|
#include "util/win/scoped_handle.h"
|
|
|
|
|
|
|
|
namespace crashpad {
|
|
|
|
namespace test {
|
|
|
|
|
|
|
|
//! \brief Manages a multiprocess test on Windows.
|
|
|
|
class WinMultiprocess {
|
|
|
|
public:
|
|
|
|
WinMultiprocess();
|
|
|
|
|
|
|
|
//! \brief Runs the test.
|
|
|
|
//!
|
|
|
|
//! This method establishes the testing environment by respawning the process
|
|
|
|
//! as a child with additional flags.
|
|
|
|
//!
|
|
|
|
//! In the parent process, WinMultiprocessParent() is run, and in the child
|
|
|
|
//! WinMultiprocessChild().
|
2015-07-31 12:31:58 -04:00
|
|
|
template <class T>
|
|
|
|
static void Run() {
|
|
|
|
ASSERT_NO_FATAL_FAILURE(
|
|
|
|
WinChildProcess::EntryPoint<ChildProcessHelper<T>>());
|
|
|
|
// If WinChildProcess::EntryPoint returns, we are in the parent process.
|
2017-03-24 15:24:11 -04:00
|
|
|
T parent_process;
|
|
|
|
WinMultiprocess* parent_multiprocess = &parent_process;
|
|
|
|
|
|
|
|
parent_multiprocess->WinMultiprocessParentBeforeChild();
|
|
|
|
|
2016-04-25 12:13:07 -07:00
|
|
|
std::unique_ptr<WinChildProcess::Handles> child_handles =
|
2015-07-31 12:31:58 -04:00
|
|
|
WinChildProcess::Launch();
|
|
|
|
ASSERT_TRUE(child_handles.get());
|
|
|
|
parent_process.child_handles_ = child_handles.get();
|
2017-03-24 15:24:11 -04:00
|
|
|
parent_multiprocess->WinMultiprocessParent();
|
2015-07-31 12:31:58 -04:00
|
|
|
|
|
|
|
// Close our side of the handles now that we're done. The child can
|
|
|
|
// use this to know when it's safe to complete.
|
|
|
|
child_handles->read.reset();
|
|
|
|
child_handles->write.reset();
|
|
|
|
|
|
|
|
// Wait for the child to complete.
|
test: Use (actual, [un]expected) in gtest {ASSERT,EXPECT}_{EQ,NE}
gtest used to require (expected, actual) ordering for arguments to
EXPECT_EQ and ASSERT_EQ, and in failed test assertions would identify
each side as “expected” or “actual.” Tests in Crashpad adhered to this
traditional ordering. After a gtest change in February 2016, it is now
agnostic with respect to the order of these arguments.
This change mechanically updates all uses of these macros to (actual,
expected) by reversing them. This provides consistency with our use of
the logging CHECK_EQ and DCHECK_EQ macros, and makes for better
readability by ordinary native speakers. The rough (but working!)
conversion tool is
https://chromium-review.googlesource.com/c/466727/1/rewrite_expectassert_eq.py,
and “git cl format” cleaned up its output.
EXPECT_NE and ASSERT_NE never had a preferred ordering. gtest never made
a judgment that one side or the other needed to provide an “unexpected”
value. Consequently, some code used (unexpected, actual) while other
code used (actual, unexpected). For consistency with the new EXPECT_EQ
and ASSERT_EQ usage, as well as consistency with CHECK_NE and DCHECK_NE,
this change also updates these use sites to (actual, unexpected) where
one side can be called “unexpected” as, for example, std::string::npos
can be. Unfortunately, this portion was a manual conversion.
References:
https://github.com/google/googletest/blob/master/googletest/docs/Primer.md#binary-comparison
https://github.com/google/googletest/commit/77d6b173380332b1c1bc540532641f410ec82d65
https://github.com/google/googletest/pull/713
Change-Id: I978fef7c94183b8b1ef63f12f5ab4d6693626be3
Reviewed-on: https://chromium-review.googlesource.com/466727
Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-04-04 00:35:21 -04:00
|
|
|
ASSERT_EQ(WaitForSingleObject(child_handles->process.get(), INFINITE),
|
|
|
|
WAIT_OBJECT_0);
|
2015-07-31 12:31:58 -04:00
|
|
|
|
|
|
|
DWORD exit_code;
|
|
|
|
ASSERT_TRUE(GetExitCodeProcess(child_handles->process.get(), &exit_code));
|
test: Use (actual, [un]expected) in gtest {ASSERT,EXPECT}_{EQ,NE}
gtest used to require (expected, actual) ordering for arguments to
EXPECT_EQ and ASSERT_EQ, and in failed test assertions would identify
each side as “expected” or “actual.” Tests in Crashpad adhered to this
traditional ordering. After a gtest change in February 2016, it is now
agnostic with respect to the order of these arguments.
This change mechanically updates all uses of these macros to (actual,
expected) by reversing them. This provides consistency with our use of
the logging CHECK_EQ and DCHECK_EQ macros, and makes for better
readability by ordinary native speakers. The rough (but working!)
conversion tool is
https://chromium-review.googlesource.com/c/466727/1/rewrite_expectassert_eq.py,
and “git cl format” cleaned up its output.
EXPECT_NE and ASSERT_NE never had a preferred ordering. gtest never made
a judgment that one side or the other needed to provide an “unexpected”
value. Consequently, some code used (unexpected, actual) while other
code used (actual, unexpected). For consistency with the new EXPECT_EQ
and ASSERT_EQ usage, as well as consistency with CHECK_NE and DCHECK_NE,
this change also updates these use sites to (actual, unexpected) where
one side can be called “unexpected” as, for example, std::string::npos
can be. Unfortunately, this portion was a manual conversion.
References:
https://github.com/google/googletest/blob/master/googletest/docs/Primer.md#binary-comparison
https://github.com/google/googletest/commit/77d6b173380332b1c1bc540532641f410ec82d65
https://github.com/google/googletest/pull/713
Change-Id: I978fef7c94183b8b1ef63f12f5ab4d6693626be3
Reviewed-on: https://chromium-review.googlesource.com/466727
Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-04-04 00:35:21 -04:00
|
|
|
ASSERT_EQ(exit_code, parent_process.exit_code_);
|
2017-03-24 15:24:11 -04:00
|
|
|
|
|
|
|
parent_multiprocess->WinMultiprocessParentAfterChild(
|
|
|
|
child_handles->process.get());
|
2015-07-31 12:31:58 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
protected:
|
|
|
|
virtual ~WinMultiprocess();
|
2015-05-28 09:04:17 -07:00
|
|
|
|
|
|
|
//! \brief Sets the expected exit code of the child process.
|
|
|
|
//!
|
|
|
|
//! The default expected termination code is `EXIT_SUCCESS` (`0`).
|
|
|
|
//!
|
doc: Fix all Doxygen warnings, cleaning up some generated documentation
This makes Doxygen’s output more actionable by setting QUIET = YES to
suppress verbose progress spew, and WARN_IF_UNDOCUMENTED = NO to prevent
warnings for undocumented classes and members from being generated. The
latter is too noisy, producing 721 warnings in the current codebase.
The remaining warnings produced by Doxygen were useful and actionable.
They fell into two categories: abuses of Doxygen’s markup syntax, and
missing (or misspelled) parameter documentation. In a small number of
cases, pass-through parameters had intentionally been left undocumented.
In these cases, they are now given blank \param descriptions. This is
not optimal, but there doesn’t appear to be any other way to tell
Doxygen to allow a single parameter to be undocumented.
Some tricky Doxygen errors were resolved by asking it to not enter
directiores that we do not provide documentation in (such as the
“on-platform” compat directories, compat/mac and compat/win, as well as
compat/non_cxx11_lib) while allowing it to enter the
“off-platform” directories that we do document (compat/non_mac and
compat/non_win).
A Doxygen run (doc/support/generate_doxygen.sh) now produces no output
at all. It would produce warnings if any were triggered.
Not directly related, but still relevant to documentation,
doc/support/generate.sh is updated to remove temporary removals of
now-extinct files and directories. doc/appengine/README is updated so
that a consistent path to “goapp” is used throughout the file.
Change-Id: I300730c04de4d3340551ea3086ca70cc5ff862d1
Reviewed-on: https://chromium-review.googlesource.com/408812
Reviewed-by: Robert Sesek <rsesek@chromium.org>
2016-11-08 14:23:09 -05:00
|
|
|
//! \param[in] exit_code The expected exit status of the child.
|
2015-05-28 09:04:17 -07:00
|
|
|
void SetExpectedChildExitCode(unsigned int exit_code);
|
|
|
|
|
|
|
|
//! \brief Returns the read pipe's file handle.
|
|
|
|
//!
|
|
|
|
//! This method may be called by either the parent or the child process.
|
|
|
|
//! Anything written to the write pipe in the partner process will appear
|
|
|
|
//! on this file handle in this process.
|
|
|
|
//!
|
|
|
|
//! It is an error to call this after CloseReadPipe() has been called.
|
|
|
|
//!
|
|
|
|
//! \return The read pipe's file handle.
|
|
|
|
FileHandle ReadPipeHandle() const;
|
|
|
|
|
|
|
|
//! \brief Returns the write pipe's file handle.
|
|
|
|
//!
|
|
|
|
//! This method may be called by either the parent or the child process.
|
|
|
|
//! Anything written to this file handle in this process will appear on
|
|
|
|
//! the read pipe in the partner process.
|
|
|
|
//!
|
|
|
|
//! It is an error to call this after CloseWritePipe() has been called.
|
|
|
|
//!
|
|
|
|
//! \return The write pipe's file handle.
|
|
|
|
FileHandle WritePipeHandle() const;
|
|
|
|
|
|
|
|
//! \brief Closes the read pipe.
|
|
|
|
//!
|
|
|
|
//! This method may be called by either the parent or the child process.
|
|
|
|
//! ReadPipeHandle() must not be called after this.
|
|
|
|
void CloseReadPipe();
|
|
|
|
|
|
|
|
//! \brief Closes the write pipe.
|
|
|
|
//!
|
|
|
|
//! This method may be called by either the parent or the child process. An
|
|
|
|
//! attempt to read from the read pipe in the partner process will indicate
|
|
|
|
//! end-of-file. WritePipeHandle() must not be called after this.
|
|
|
|
void CloseWritePipe();
|
|
|
|
|
|
|
|
//! \brief Returns a handle to the child process.
|
|
|
|
//!
|
|
|
|
//! This method may only be called by the parent process.
|
|
|
|
HANDLE ChildProcess() const;
|
|
|
|
|
|
|
|
private:
|
2015-07-31 12:31:58 -04:00
|
|
|
// Implements an adapter to provide WinMultiprocess with access to the
|
|
|
|
// anonymous pipe handles from WinChildProcess.
|
|
|
|
class ChildProcessHelperBase : public WinChildProcess {
|
|
|
|
public:
|
|
|
|
ChildProcessHelperBase() {}
|
|
|
|
~ChildProcessHelperBase() override {}
|
|
|
|
|
|
|
|
void CloseWritePipeForwarder() { CloseWritePipe(); }
|
|
|
|
void CloseReadPipeForwarder() { CloseReadPipe(); }
|
|
|
|
FileHandle ReadPipeHandleForwarder() const { return ReadPipeHandle(); }
|
|
|
|
FileHandle WritePipeHandleForwarder() const { return WritePipeHandle(); }
|
|
|
|
|
|
|
|
private:
|
|
|
|
DISALLOW_COPY_AND_ASSIGN(ChildProcessHelperBase);
|
|
|
|
};
|
|
|
|
|
|
|
|
// Forwards WinChildProcess::Run to T::WinMultiprocessChild.
|
|
|
|
template <class T>
|
|
|
|
class ChildProcessHelper : public ChildProcessHelperBase {
|
|
|
|
public:
|
|
|
|
ChildProcessHelper() {}
|
|
|
|
~ChildProcessHelper() override {}
|
|
|
|
|
|
|
|
private:
|
|
|
|
int Run() override {
|
|
|
|
T child_process;
|
|
|
|
child_process.child_process_helper_ = this;
|
|
|
|
static_cast<WinMultiprocess*>(&child_process)->WinMultiprocessChild();
|
|
|
|
if (testing::Test::HasFailure())
|
|
|
|
return 255;
|
|
|
|
return EXIT_SUCCESS;
|
|
|
|
}
|
|
|
|
|
|
|
|
DISALLOW_COPY_AND_ASSIGN(ChildProcessHelper);
|
|
|
|
};
|
|
|
|
|
2015-05-28 09:04:17 -07:00
|
|
|
//! \brief The subclass-provided parent routine.
|
|
|
|
//!
|
2020-05-06 20:39:19 -04:00
|
|
|
//! Test failures should be reported via Google Test: `EXPECT_*()`,
|
|
|
|
//! `ASSERT_*()`, `FAIL()`, etc.
|
2015-05-28 09:04:17 -07:00
|
|
|
//!
|
|
|
|
//! This method need not use `WaitForSingleObject()`-family call to wait for
|
|
|
|
//! the child process to exit, as this is handled by this class.
|
|
|
|
//!
|
|
|
|
//! Subclasses must implement this method to define how the parent operates.
|
|
|
|
virtual void WinMultiprocessParent() = 0;
|
|
|
|
|
2017-03-24 15:24:11 -04:00
|
|
|
//! \brief The optional routine run in parent before the child is spawned.
|
|
|
|
//!
|
|
|
|
//! Subclasses may implement this method to prepare the environment for
|
|
|
|
//! the child process.
|
|
|
|
virtual void WinMultiprocessParentBeforeChild() {}
|
|
|
|
|
|
|
|
//! \brief The optional routine run in parent after the child exits.
|
|
|
|
//!
|
|
|
|
//! Subclasses may implement this method to clean up the environment after
|
|
|
|
//! the child process has exited.
|
|
|
|
//!
|
|
|
|
//! \param[in] child A handle to the exited child process.
|
|
|
|
virtual void WinMultiprocessParentAfterChild(HANDLE child) {}
|
|
|
|
|
2015-05-28 09:04:17 -07:00
|
|
|
//! \brief The subclass-provided child routine.
|
|
|
|
//!
|
2020-05-06 20:39:19 -04:00
|
|
|
//! Test failures should be reported via Google Test: `EXPECT_*()`,
|
|
|
|
//! `ASSERT_*()`, `FAIL()`, etc.
|
2015-05-28 09:04:17 -07:00
|
|
|
//!
|
|
|
|
//! Subclasses must implement this method to define how the child operates.
|
|
|
|
//! Subclasses may exit with a failure status by using `LOG(FATAL)`,
|
|
|
|
//! `abort()`, or similar. They may exit cleanly by returning from this
|
|
|
|
//! method.
|
|
|
|
virtual void WinMultiprocessChild() = 0;
|
|
|
|
|
|
|
|
unsigned int exit_code_;
|
2015-07-31 12:31:58 -04:00
|
|
|
WinChildProcess::Handles* child_handles_;
|
|
|
|
ChildProcessHelperBase* child_process_helper_;
|
2015-05-28 09:04:17 -07:00
|
|
|
|
|
|
|
DISALLOW_COPY_AND_ASSIGN(WinMultiprocess);
|
|
|
|
};
|
|
|
|
|
|
|
|
} // namespace test
|
|
|
|
} // namespace crashpad
|
|
|
|
|
|
|
|
#endif // CRASHPAD_TEST_WIN_WIN_MULTIPROCESS_H_
|