2015-03-11 17:07:11 -04: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.
|
|
|
|
|
|
2015-05-01 13:48:23 -07:00
|
|
|
|
#include "snapshot/crashpad_info_client_options.h"
|
2015-03-11 17:07:11 -04:00
|
|
|
|
|
|
|
|
|
#include "base/files/file_path.h"
|
2016-01-06 12:22:50 -05:00
|
|
|
|
#include "base/macros.h"
|
2015-05-01 15:49:35 -07:00
|
|
|
|
#include "base/strings/utf_string_conversions.h"
|
2015-05-01 13:48:23 -07:00
|
|
|
|
#include "build/build_config.h"
|
2015-03-11 17:07:11 -04:00
|
|
|
|
#include "client/crashpad_info.h"
|
|
|
|
|
#include "gtest/gtest.h"
|
2015-05-01 13:48:23 -07:00
|
|
|
|
#include "test/errors.h"
|
2017-04-03 13:53:11 -04:00
|
|
|
|
#include "test/test_paths.h"
|
2015-03-11 17:07:11 -04:00
|
|
|
|
|
2015-05-01 13:48:23 -07:00
|
|
|
|
#if defined(OS_MACOSX)
|
|
|
|
|
#include <dlfcn.h>
|
|
|
|
|
#include "snapshot/mac/process_snapshot_mac.h"
|
|
|
|
|
#elif defined(OS_WIN)
|
|
|
|
|
#include <windows.h>
|
|
|
|
|
#include "snapshot/win/process_snapshot_win.h"
|
|
|
|
|
#endif
|
|
|
|
|
|
2015-03-11 17:07:11 -04:00
|
|
|
|
namespace crashpad {
|
|
|
|
|
namespace test {
|
|
|
|
|
namespace {
|
|
|
|
|
|
|
|
|
|
TEST(CrashpadInfoClientOptions, TriStateFromCrashpadInfo) {
|
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
|
|
|
|
EXPECT_EQ(CrashpadInfoClientOptions::TriStateFromCrashpadInfo(0),
|
|
|
|
|
TriState::kUnset);
|
|
|
|
|
EXPECT_EQ(CrashpadInfoClientOptions::TriStateFromCrashpadInfo(1),
|
|
|
|
|
TriState::kEnabled);
|
|
|
|
|
EXPECT_EQ(CrashpadInfoClientOptions::TriStateFromCrashpadInfo(2),
|
|
|
|
|
TriState::kDisabled);
|
2015-03-11 17:07:11 -04:00
|
|
|
|
|
|
|
|
|
// These will produce log messages but should result in kUnset being returned.
|
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
|
|
|
|
EXPECT_EQ(CrashpadInfoClientOptions::TriStateFromCrashpadInfo(3),
|
|
|
|
|
TriState::kUnset);
|
|
|
|
|
EXPECT_EQ(CrashpadInfoClientOptions::TriStateFromCrashpadInfo(4),
|
|
|
|
|
TriState::kUnset);
|
|
|
|
|
EXPECT_EQ(CrashpadInfoClientOptions::TriStateFromCrashpadInfo(0xff),
|
|
|
|
|
TriState::kUnset);
|
2015-03-11 17:07:11 -04:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
class ScopedUnsetCrashpadInfoOptions {
|
|
|
|
|
public:
|
|
|
|
|
explicit ScopedUnsetCrashpadInfoOptions(CrashpadInfo* crashpad_info)
|
|
|
|
|
: crashpad_info_(crashpad_info) {
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
~ScopedUnsetCrashpadInfoOptions() {
|
|
|
|
|
crashpad_info_->set_crashpad_handler_behavior(TriState::kUnset);
|
|
|
|
|
crashpad_info_->set_system_crash_reporter_forwarding(TriState::kUnset);
|
2016-04-21 22:19:31 -07:00
|
|
|
|
crashpad_info_->set_gather_indirectly_referenced_memory(TriState::kUnset,
|
|
|
|
|
0);
|
2015-03-11 17:07:11 -04:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
private:
|
|
|
|
|
CrashpadInfo* crashpad_info_;
|
|
|
|
|
|
|
|
|
|
DISALLOW_COPY_AND_ASSIGN(ScopedUnsetCrashpadInfoOptions);
|
|
|
|
|
};
|
|
|
|
|
|
2016-01-14 12:50:22 -08:00
|
|
|
|
CrashpadInfoClientOptions SelfProcessSnapshotAndGetCrashpadOptions() {
|
2015-05-01 13:48:23 -07:00
|
|
|
|
#if defined(OS_MACOSX)
|
2015-03-11 17:07:11 -04:00
|
|
|
|
ProcessSnapshotMac process_snapshot;
|
2016-01-14 12:50:22 -08:00
|
|
|
|
EXPECT_TRUE(process_snapshot.Initialize(mach_task_self()));
|
2015-05-01 13:48:23 -07:00
|
|
|
|
#elif defined(OS_WIN)
|
|
|
|
|
ProcessSnapshotWin process_snapshot;
|
2016-01-14 12:50:22 -08:00
|
|
|
|
EXPECT_TRUE(process_snapshot.Initialize(
|
2016-05-02 11:36:41 -07:00
|
|
|
|
GetCurrentProcess(), ProcessSuspensionState::kRunning, 0, 0));
|
2015-05-01 13:48:23 -07:00
|
|
|
|
#else
|
|
|
|
|
#error Port.
|
|
|
|
|
#endif // OS_MACOSX
|
2015-03-11 17:07:11 -04:00
|
|
|
|
|
|
|
|
|
CrashpadInfoClientOptions options;
|
|
|
|
|
process_snapshot.GetCrashpadOptions(&options);
|
2016-01-14 12:50:22 -08:00
|
|
|
|
return options;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
TEST(CrashpadInfoClientOptions, OneModule) {
|
|
|
|
|
// Make sure that the initial state has all values unset.
|
|
|
|
|
auto options = SelfProcessSnapshotAndGetCrashpadOptions();
|
2015-03-11 17:07:11 -04:00
|
|
|
|
|
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
|
|
|
|
EXPECT_EQ(options.crashpad_handler_behavior, TriState::kUnset);
|
|
|
|
|
EXPECT_EQ(options.system_crash_reporter_forwarding, TriState::kUnset);
|
|
|
|
|
EXPECT_EQ(options.gather_indirectly_referenced_memory, TriState::kUnset);
|
|
|
|
|
EXPECT_EQ(options.indirectly_referenced_memory_cap, 0u);
|
2015-03-11 17:07:11 -04:00
|
|
|
|
|
|
|
|
|
CrashpadInfo* crashpad_info = CrashpadInfo::GetCrashpadInfo();
|
|
|
|
|
ASSERT_TRUE(crashpad_info);
|
|
|
|
|
|
|
|
|
|
{
|
|
|
|
|
ScopedUnsetCrashpadInfoOptions unset(crashpad_info);
|
|
|
|
|
|
|
|
|
|
crashpad_info->set_crashpad_handler_behavior(TriState::kEnabled);
|
|
|
|
|
|
2016-01-14 12:50:22 -08:00
|
|
|
|
options = SelfProcessSnapshotAndGetCrashpadOptions();
|
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
|
|
|
|
EXPECT_EQ(options.crashpad_handler_behavior, TriState::kEnabled);
|
|
|
|
|
EXPECT_EQ(options.system_crash_reporter_forwarding, TriState::kUnset);
|
|
|
|
|
EXPECT_EQ(options.gather_indirectly_referenced_memory, TriState::kUnset);
|
|
|
|
|
EXPECT_EQ(options.indirectly_referenced_memory_cap, 0u);
|
2015-03-11 17:07:11 -04:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
{
|
|
|
|
|
ScopedUnsetCrashpadInfoOptions unset(crashpad_info);
|
|
|
|
|
|
|
|
|
|
crashpad_info->set_system_crash_reporter_forwarding(TriState::kDisabled);
|
|
|
|
|
|
2016-01-14 12:50:22 -08:00
|
|
|
|
options = SelfProcessSnapshotAndGetCrashpadOptions();
|
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
|
|
|
|
EXPECT_EQ(options.crashpad_handler_behavior, TriState::kUnset);
|
|
|
|
|
EXPECT_EQ(options.system_crash_reporter_forwarding, TriState::kDisabled);
|
|
|
|
|
EXPECT_EQ(options.gather_indirectly_referenced_memory, TriState::kUnset);
|
|
|
|
|
EXPECT_EQ(options.indirectly_referenced_memory_cap, 0u);
|
2016-01-14 15:12:28 -08:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
{
|
|
|
|
|
ScopedUnsetCrashpadInfoOptions unset(crashpad_info);
|
|
|
|
|
|
2016-04-21 22:19:31 -07:00
|
|
|
|
crashpad_info->set_gather_indirectly_referenced_memory(TriState::kEnabled,
|
|
|
|
|
1234);
|
2016-01-14 15:12:28 -08:00
|
|
|
|
|
2016-01-14 12:50:22 -08:00
|
|
|
|
options = SelfProcessSnapshotAndGetCrashpadOptions();
|
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
|
|
|
|
EXPECT_EQ(options.crashpad_handler_behavior, TriState::kUnset);
|
|
|
|
|
EXPECT_EQ(options.system_crash_reporter_forwarding, TriState::kUnset);
|
|
|
|
|
EXPECT_EQ(options.gather_indirectly_referenced_memory, TriState::kEnabled);
|
|
|
|
|
EXPECT_EQ(options.indirectly_referenced_memory_cap, 1234u);
|
2015-03-11 17:07:11 -04:00
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2015-05-01 13:48:23 -07:00
|
|
|
|
#if defined(OS_POSIX)
|
|
|
|
|
using DlHandle = void*;
|
|
|
|
|
#elif defined(OS_WIN)
|
|
|
|
|
using DlHandle = HMODULE;
|
|
|
|
|
#endif // OS_POSIX
|
|
|
|
|
|
2015-03-11 17:07:11 -04:00
|
|
|
|
class ScopedDlHandle {
|
|
|
|
|
public:
|
2015-05-01 13:48:23 -07:00
|
|
|
|
explicit ScopedDlHandle(DlHandle dl_handle)
|
2015-03-11 17:07:11 -04:00
|
|
|
|
: dl_handle_(dl_handle) {
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
~ScopedDlHandle() {
|
|
|
|
|
if (dl_handle_) {
|
2015-05-01 13:48:23 -07:00
|
|
|
|
#if defined(OS_POSIX)
|
2015-03-11 17:07:11 -04:00
|
|
|
|
if (dlclose(dl_handle_) != 0) {
|
|
|
|
|
LOG(ERROR) << "dlclose: " << dlerror();
|
|
|
|
|
}
|
2015-05-01 13:48:23 -07:00
|
|
|
|
#elif defined(OS_WIN)
|
|
|
|
|
if (!FreeLibrary(dl_handle_))
|
|
|
|
|
PLOG(ERROR) << "FreeLibrary";
|
|
|
|
|
#endif // OS_POSIX
|
2015-03-11 17:07:11 -04:00
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
bool valid() const { return dl_handle_ != nullptr; }
|
|
|
|
|
|
|
|
|
|
template <typename T>
|
|
|
|
|
T LookUpSymbol(const char* symbol_name) {
|
2015-05-01 13:48:23 -07:00
|
|
|
|
#if defined(OS_POSIX)
|
2015-03-11 17:07:11 -04:00
|
|
|
|
return reinterpret_cast<T>(dlsym(dl_handle_, symbol_name));
|
2015-05-01 13:48:23 -07:00
|
|
|
|
#elif defined(OS_WIN)
|
|
|
|
|
return reinterpret_cast<T>(GetProcAddress(dl_handle_, symbol_name));
|
|
|
|
|
#endif // OS_POSIX
|
2015-03-11 17:07:11 -04:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
private:
|
2015-05-01 13:48:23 -07:00
|
|
|
|
DlHandle dl_handle_;
|
2015-03-11 17:07:11 -04:00
|
|
|
|
|
|
|
|
|
DISALLOW_COPY_AND_ASSIGN(ScopedDlHandle);
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
TEST(CrashpadInfoClientOptions, TwoModules) {
|
|
|
|
|
// Open the module, which has its own CrashpadInfo structure.
|
2015-05-01 13:48:23 -07:00
|
|
|
|
#if defined(OS_MACOSX)
|
|
|
|
|
const base::FilePath::StringType kDlExtension = FILE_PATH_LITERAL(".so");
|
|
|
|
|
#elif defined(OS_WIN)
|
|
|
|
|
const base::FilePath::StringType kDlExtension = FILE_PATH_LITERAL(".dll");
|
|
|
|
|
#endif
|
2017-04-03 13:53:11 -04:00
|
|
|
|
base::FilePath module_path = TestPaths::Executable().DirName().Append(
|
2015-05-01 13:48:23 -07:00
|
|
|
|
FILE_PATH_LITERAL("crashpad_snapshot_test_module") + kDlExtension);
|
|
|
|
|
#if defined(OS_MACOSX)
|
2015-03-11 17:07:11 -04:00
|
|
|
|
ScopedDlHandle dl_handle(
|
|
|
|
|
dlopen(module_path.value().c_str(), RTLD_LAZY | RTLD_LOCAL));
|
|
|
|
|
ASSERT_TRUE(dl_handle.valid()) << "dlopen " << module_path.value() << ": "
|
|
|
|
|
<< dlerror();
|
2015-05-01 13:48:23 -07:00
|
|
|
|
#elif defined(OS_WIN)
|
|
|
|
|
ScopedDlHandle dl_handle(LoadLibrary(module_path.value().c_str()));
|
2015-05-01 15:49:35 -07:00
|
|
|
|
ASSERT_TRUE(dl_handle.valid())
|
|
|
|
|
<< "LoadLibrary " << base::UTF16ToUTF8(module_path.value()) << ": "
|
|
|
|
|
<< ErrorMessage();
|
2015-05-01 13:48:23 -07:00
|
|
|
|
#else
|
|
|
|
|
#error Port.
|
|
|
|
|
#endif // OS_MACOSX
|
2015-03-11 17:07:11 -04:00
|
|
|
|
|
|
|
|
|
// Get the function pointer from the module. This wraps GetCrashpadInfo(), but
|
|
|
|
|
// because it runs in the module, it returns the remote module’s CrashpadInfo
|
|
|
|
|
// structure.
|
|
|
|
|
CrashpadInfo* (*TestModule_GetCrashpadInfo)() =
|
|
|
|
|
dl_handle.LookUpSymbol<CrashpadInfo* (*)()>("TestModule_GetCrashpadInfo");
|
|
|
|
|
ASSERT_TRUE(TestModule_GetCrashpadInfo);
|
|
|
|
|
|
2016-01-14 12:50:22 -08:00
|
|
|
|
auto options = SelfProcessSnapshotAndGetCrashpadOptions();
|
2015-03-11 17:07:11 -04:00
|
|
|
|
|
2016-01-14 12:50:22 -08:00
|
|
|
|
// Make sure that the initial state has all values unset.
|
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
|
|
|
|
EXPECT_EQ(options.crashpad_handler_behavior, TriState::kUnset);
|
|
|
|
|
EXPECT_EQ(options.system_crash_reporter_forwarding, TriState::kUnset);
|
|
|
|
|
EXPECT_EQ(options.gather_indirectly_referenced_memory, TriState::kUnset);
|
2015-03-11 17:07:11 -04:00
|
|
|
|
|
|
|
|
|
// Get both CrashpadInfo structures.
|
|
|
|
|
CrashpadInfo* local_crashpad_info = CrashpadInfo::GetCrashpadInfo();
|
|
|
|
|
ASSERT_TRUE(local_crashpad_info);
|
|
|
|
|
|
|
|
|
|
CrashpadInfo* remote_crashpad_info = TestModule_GetCrashpadInfo();
|
|
|
|
|
ASSERT_TRUE(remote_crashpad_info);
|
|
|
|
|
|
|
|
|
|
{
|
|
|
|
|
ScopedUnsetCrashpadInfoOptions unset_local(local_crashpad_info);
|
|
|
|
|
ScopedUnsetCrashpadInfoOptions unset_remote(remote_crashpad_info);
|
|
|
|
|
|
|
|
|
|
// When only one module sets a value, it applies to the entire process.
|
|
|
|
|
remote_crashpad_info->set_crashpad_handler_behavior(TriState::kEnabled);
|
|
|
|
|
|
2016-01-14 12:50:22 -08:00
|
|
|
|
options = SelfProcessSnapshotAndGetCrashpadOptions();
|
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
|
|
|
|
EXPECT_EQ(options.crashpad_handler_behavior, TriState::kEnabled);
|
|
|
|
|
EXPECT_EQ(options.system_crash_reporter_forwarding, TriState::kUnset);
|
|
|
|
|
EXPECT_EQ(options.gather_indirectly_referenced_memory, TriState::kUnset);
|
2015-03-11 17:07:11 -04:00
|
|
|
|
|
|
|
|
|
// When more than one module sets a value, the first one in the module list
|
|
|
|
|
// applies to the process. The local module should appear before the remote
|
|
|
|
|
// module, because the local module loaded the remote module.
|
|
|
|
|
local_crashpad_info->set_crashpad_handler_behavior(TriState::kDisabled);
|
|
|
|
|
|
2016-01-14 12:50:22 -08:00
|
|
|
|
options = SelfProcessSnapshotAndGetCrashpadOptions();
|
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
|
|
|
|
EXPECT_EQ(options.crashpad_handler_behavior, TriState::kDisabled);
|
|
|
|
|
EXPECT_EQ(options.system_crash_reporter_forwarding, TriState::kUnset);
|
|
|
|
|
EXPECT_EQ(options.gather_indirectly_referenced_memory, TriState::kUnset);
|
2015-03-11 17:07:11 -04:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
{
|
|
|
|
|
ScopedUnsetCrashpadInfoOptions unset_local(local_crashpad_info);
|
|
|
|
|
ScopedUnsetCrashpadInfoOptions unset_remote(remote_crashpad_info);
|
|
|
|
|
|
|
|
|
|
// When only one module sets a value, it applies to the entire process.
|
|
|
|
|
remote_crashpad_info->set_system_crash_reporter_forwarding(
|
|
|
|
|
TriState::kDisabled);
|
|
|
|
|
|
2016-01-14 12:50:22 -08:00
|
|
|
|
options = SelfProcessSnapshotAndGetCrashpadOptions();
|
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
|
|
|
|
EXPECT_EQ(options.crashpad_handler_behavior, TriState::kUnset);
|
|
|
|
|
EXPECT_EQ(options.system_crash_reporter_forwarding, TriState::kDisabled);
|
|
|
|
|
EXPECT_EQ(options.gather_indirectly_referenced_memory, TriState::kUnset);
|
2015-03-11 17:07:11 -04:00
|
|
|
|
|
|
|
|
|
// When more than one module sets a value, the first one in the module list
|
|
|
|
|
// applies to the process. The local module should appear before the remote
|
|
|
|
|
// module, because the local module loaded the remote module.
|
|
|
|
|
local_crashpad_info->set_system_crash_reporter_forwarding(
|
|
|
|
|
TriState::kEnabled);
|
|
|
|
|
|
2016-01-14 12:50:22 -08:00
|
|
|
|
options = SelfProcessSnapshotAndGetCrashpadOptions();
|
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
|
|
|
|
EXPECT_EQ(options.crashpad_handler_behavior, TriState::kUnset);
|
|
|
|
|
EXPECT_EQ(options.system_crash_reporter_forwarding, TriState::kEnabled);
|
|
|
|
|
EXPECT_EQ(options.gather_indirectly_referenced_memory, TriState::kUnset);
|
2015-03-11 17:07:11 -04:00
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
} // namespace
|
|
|
|
|
} // namespace test
|
|
|
|
|
} // namespace crashpad
|