3party/crashpad
0
0
Fork 0
mirror of https://github.com/chromium/crashpad.git synced 2024-12-27 15:32:10 +08:00
Code Issues Projects Releases Wiki Activity
crashpad/snapshot/BUILD.gn

660 lines
20 KiB
Plaintext
Raw Normal View History

Update copyright boilerplate, 2022 edition (Crashpad) sed -i '' -E -e 's/Copyright (.+) The Crashpad Authors\. All rights reserved\.$/Copyright \1 The Crashpad Authors/' $(git grep -El 'Copyright (.+) The Crashpad Authors\. All rights reserved\.$') Bug: chromium:1098010 Change-Id: I8d6138469ddbe3d281a5d83f64cf918ec2491611 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3878262 Reviewed-by: Joshua Peraza <jperaza@chromium.org> Commit-Queue: Mark Mentovai <mark@chromium.org>
2022-09-06 19:14:07 -04:00
# Copyright 2015 The Crashpad Authors
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
#
# 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.
gn: Avoid depending on BUILDCONFIG.gn globals Goes with https://chromium-review.googlesource.com/c/chromium/mini_chromium/+/834648. Includes mini_chromium DEPS roll to pull in https://chromium.googlesource.com/chromium/mini_chromium/+/edfe51ce818e55eae73ab3f144a360e855533888 Bug: crashpad:79, crashpad:196 Change-Id: Ib45cc738aecf9ae727f8faeff81f3b71e2dc9de8 Reviewed-on: https://chromium-review.googlesource.com/834543 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2017-12-19 15:31:04 -08:00
import("../build/crashpad_buildconfig.gni")
Add libfuzzer support Adds the build support for using libfuzzer controlled by setting `crashpad_use_libfuzzer=true`. Also adds a first fuzzer (for ElfImageReader). Currently only runs on Linux, but should work on Fuchsia too with some minor fixes (not sure yet whether the fixes required are toolchain or in our build setup). Run as: out/lin/elf_image_reader_fuzzer snapshot/elf/elf_image_reader_fuzzer_corpus/ hits an OOM pretty quickly in trying to allocate a giant buffer. Bug: crashpad:30, crashpad:196, crashpad:233 Change-Id: Idd3ca11fe00319b8b29e029d5e13b17bfd518ea0 Reviewed-on: https://chromium-review.googlesource.com/1083451 Reviewed-by: Robert Sesek <rsesek@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2018-06-04 16:16:19 -07:00
import("../build/crashpad_fuzzer_test.gni")
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
gn: Fix symbol_level use in chromium style Bug: crashpad:79 Change-Id: I417f17194ee1a8ef157ea1e67e64878ccb6f5c10 Reviewed-on: https://chromium-review.googlesource.com/835528 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-12-19 17:15:10 -08:00
if (crashpad_is_in_chromium) {
import("//build/config/compiler/compiler.gni")
}
fuchsia: Centralize disabling of Wconversion Because of the multiple-worlds building of the Crashpad code in the Fuchsia tree (with the Fuchsia BUILDCONFIG.gn in particular) there's no good location to globally disable Wconversion for all of crashpad. This can be somewhat-improved by using a GN template crashpad_static_library() similar to the existing crashpad_executable() template. Includes mini_chromium DEPS roll: 68da43e Fix a couple trucation warnings 88ce866 build: set include dirs Bug: fuchsia:58162 Change-Id: I638fcf858c35b9a858ca2c410636f8c99603aed2 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2411131 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2020-09-14 14:22:05 -07:00
crashpad_static_library("snapshot") {
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
sources = [
"annotation_snapshot.cc",
"annotation_snapshot.h",
"capture_memory.cc",
"capture_memory.h",
"crashpad_info_client_options.cc",
"crashpad_info_client_options.h",
"exception_snapshot.h",
"handle_snapshot.cc",
"handle_snapshot.h",
Coalesce memory ranges Follows https://chromium-review.googlesource.com/c/374019/. Causes MinidumpMemoryListWriter to merge all overlapping ranges before writing the MINIDUMP_MEMORY_LIST. This is: 1) Necessary for the Google internal crash processor, which in some cases attempts to read the raw memory (displaying ASAN red zones), and aborts if there are any overlapping ranges in the minidump on load; 2) Necessary for new-ish versions of windbg (see bug 216 below). It is believed that this is a change in behavior in the tool that made dumps with overlapping ranges unreadable; 3) More efficient. The .dmp for crashy_program goes from 306K to 140K with this enabled. In Chrome minidumps where set_gather_indirectly_referenced_memory() is used (in practice this means Chrome Windows Beta, Dev, and Canary), the savings are expected to be substantial. Bug: crashpad:61, chromium:638370, crashpad:216 Change-Id: I969e1a52da555ceba59a727d933bfeef6787c7a5 Reviewed-on: https://chromium-review.googlesource.com/374539 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-02-01 15:54:56 -08:00
"memory_snapshot.cc",
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
"memory_snapshot.h",
Pull (most) platform-specific MemorySnapshots out Pulls the concrete non-test implementations of MemorySnapshot out into a template. They were effectively identical on Mac and Linux/Android, and I was going to have to add another identical one for Fuchsia. Unfortunately it needs to be a template because of the snapshot merging template it calls that needs the platform-specific ProcessReader (so it can't just pass in a base ProcessMemory in initialization instead). This is used on Mac, Linux, Android, and Fuchsia, but there is still a Windows implementation (different because its ProcessReader is a bit different) and a test implementation. Bug: crashpad:196 Change-Id: I4b5575fee0749e96b08e756be1f8380a2c994d7c Reviewed-on: https://chromium-review.googlesource.com/929308 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2018-02-21 16:07:17 -08:00
"memory_snapshot_generic.h",
Add ExceptionSnapshotMinidump. Implemented all of the interface except Context(). Bug: crashpad:10 Change-Id: If76e539fd7b995da50f83e02f095f05537f5572a Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/1567489 Commit-Queue: Peter Wen <wnwen@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org> Reviewed-by: Casey Dahlin <sadmac@google.com>
2019-04-17 12:54:06 -04:00
"minidump/exception_snapshot_minidump.cc",
"minidump/exception_snapshot_minidump.h",
Add ProcessSnapshotMinidump::CustomMinidumpStreams() Add a method to ProcessSnapshotMinidump to expose a similar interface to ModuleSnapshot::CustomMinidumpStreams(). It's implemented on the process snapshot here because there is no way to map custom minidump streams back to a specific module. This allows implementing tests that inspect custom user streams in minidumps. Bug: 896019 Change-Id: I1673c342753e13d64bddcc0083ca29fa356deac7 Reviewed-on: https://chromium-review.googlesource.com/c/1271405 Commit-Queue: Vlad Tsyrklevich <vtsyrklevich@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-11-16 20:41:17 -08:00
"minidump/memory_snapshot_minidump.cc",
"minidump/memory_snapshot_minidump.h",
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
"minidump/minidump_annotation_reader.cc",
"minidump/minidump_annotation_reader.h",
Implement Exception context for minidump Bug: crashpad:10 Change-Id: I90d72d813da11d25c1ed13a51daacec9b0ad4a0f Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/1753063 Commit-Queue: Casey Dahlin <sadmac@google.com> Reviewed-by: Scott Graham <scottmg@chromium.org>
2019-08-13 15:14:20 -07:00
"minidump/minidump_context_converter.cc",
"minidump/minidump_context_converter.h",
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
"minidump/minidump_simple_string_dictionary_reader.cc",
"minidump/minidump_simple_string_dictionary_reader.h",
Add ProcessSnapshotMinidump::CustomMinidumpStreams() Add a method to ProcessSnapshotMinidump to expose a similar interface to ModuleSnapshot::CustomMinidumpStreams(). It's implemented on the process snapshot here because there is no way to map custom minidump streams back to a specific module. This allows implementing tests that inspect custom user streams in minidumps. Bug: 896019 Change-Id: I1673c342753e13d64bddcc0083ca29fa356deac7 Reviewed-on: https://chromium-review.googlesource.com/c/1271405 Commit-Queue: Vlad Tsyrklevich <vtsyrklevich@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-11-16 20:41:17 -08:00
"minidump/minidump_stream.h",
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
"minidump/minidump_string_list_reader.cc",
"minidump/minidump_string_list_reader.h",
"minidump/minidump_string_reader.cc",
"minidump/minidump_string_reader.h",
"minidump/module_snapshot_minidump.cc",
"minidump/module_snapshot_minidump.h",
"minidump/process_snapshot_minidump.cc",
"minidump/process_snapshot_minidump.h",
Add SystemSnapshotMinidump Only partially implemented, but we can get most of the useful stuff, including CPU Architecture. Bug: crashpad:10 Change-Id: I727eeef5770430253a45cd046a66488f743ac25a Reviewed-on: https://chromium-review.googlesource.com/c/1285033 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org>
2018-10-15 15:20:48 -07:00
"minidump/system_snapshot_minidump.cc",
"minidump/system_snapshot_minidump.h",
Add ThreadSnapshotMinidump Only partially implemented, but ProcessSnapshotMinidump now returns them appropriately. Bug: crashpad:10 Change-Id: I44f598256965e404f62bd93e9e2efc61527298db Reviewed-on: https://chromium-review.googlesource.com/c/1278280 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org>
2018-10-12 13:12:01 -07:00
"minidump/thread_snapshot_minidump.cc",
"minidump/thread_snapshot_minidump.h",
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
"module_snapshot.h",
"process_snapshot.h",
"snapshot_constants.h",
"system_snapshot.h",
"thread_snapshot.h",
"unloaded_module_snapshot.cc",
"unloaded_module_snapshot.h",
]
Prepare for removal of is_posix from the Fuchsia build This also rolls crashpad/third_party/mini_chromium/mini_chromium/ d42eb4101..6e0fdb2e4 (2 commits) https://chromium.googlesource.com/chromium/mini_chromium/+log/d42eb4101236..6e0fdb2e4966 $ git log d42eb4101..6e0fdb2e4 --date=short --no-merges --format='%ad %ae %s' 2018-04-04 scottmg@chromium.org Repair Linux-with-sysroot build after clang update 2018-04-04 fdegans Prepare for |is_posix| switch in the Fuchsia build Created with: roll-dep crashpad/third_party/mini_chromium/mini_chromium Bug: chromium:812974 Change-Id: I3d8efc3124c97981eda63f104a7adfb670babab7 Reviewed-on: https://chromium-review.googlesource.com/988231 Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-04-04 15:12:50 -07:00
if (crashpad_is_posix || crashpad_is_fuchsia) {
gn win: Get main test binaries building - default to subsystem:console - don't build posix/timezone.* - add some missing libs This gets all the main binaries building and running. Most configs pass, but there's some offsets that seem different in some builds; need to investigate more. Additionally, the binaries used by end_to_end_test.py aren't yet built, so that script fails. Includes mini_chromium roll to 46eeaf9: 46eea49 gn win: Add debug info and pdb to cc/cxx 902a29f gn win: Various fixes towards making GN build work Bug: crashpad:79 Change-Id: Ie56a469b84bed7b0330172cec9f1a8aeb95f702e Reviewed-on: https://chromium-review.googlesource.com/902403 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-02-06 10:57:23 -08:00
sources += [
"posix/timezone.cc",
"posix/timezone.h",
]
}
gn: Avoid depending on BUILDCONFIG.gn globals Goes with https://chromium-review.googlesource.com/c/chromium/mini_chromium/+/834648. Includes mini_chromium DEPS roll to pull in https://chromium.googlesource.com/chromium/mini_chromium/+/edfe51ce818e55eae73ab3f144a360e855533888 Bug: crashpad:79, crashpad:196 Change-Id: Ib45cc738aecf9ae727f8faeff81f3b71e2dc9de8 Reviewed-on: https://chromium-review.googlesource.com/834543 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2017-12-19 15:31:04 -08:00
if (crashpad_is_mac) {
gn: Move sources out to explicit blocks This avoids relying on set_sources_assignment_filter, and so gets closer to a correct set of files to build on Fuchsia. Bug: crashpad:79, crashpad:196 Change-Id: Ib7daa5137935113c6645b72eb1dedd943a9db96e Reviewed-on: https://chromium-review.googlesource.com/797672 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-29 11:59:18 -08:00
sources += [
"mac/cpu_context_mac.cc",
"mac/cpu_context_mac.h",
"mac/exception_snapshot_mac.cc",
"mac/exception_snapshot_mac.h",
"mac/mach_o_image_annotations_reader.cc",
"mac/mach_o_image_annotations_reader.h",
"mac/mach_o_image_reader.cc",
"mac/mach_o_image_reader.h",
"mac/mach_o_image_segment_reader.cc",
"mac/mach_o_image_segment_reader.h",
"mac/mach_o_image_symbol_table_reader.cc",
"mac/mach_o_image_symbol_table_reader.h",
"mac/module_snapshot_mac.cc",
"mac/module_snapshot_mac.h",
Rename ProcessReader to platform-suffixed versions Mac's ProcessReader becomes ProcessReaderMac. Linux/Android's ProcessReader becomes ProcessReaderLinux. Fuchsia's ProcessReader becomes ProcessReaderFuchsia. No intended change in behavior. Bug: crashpad:196, crashpad:30 Change-Id: I7ec8d72f79533bd78189173261ade2ad99010bad Reviewed-on: https://chromium-review.googlesource.com/930321 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2018-02-22 12:12:26 -08:00
"mac/process_reader_mac.cc",
"mac/process_reader_mac.h",
gn: Move sources out to explicit blocks This avoids relying on set_sources_assignment_filter, and so gets closer to a correct set of files to build on Fuchsia. Bug: crashpad:79, crashpad:196 Change-Id: Ib7daa5137935113c6645b72eb1dedd943a9db96e Reviewed-on: https://chromium-review.googlesource.com/797672 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-29 11:59:18 -08:00
"mac/process_snapshot_mac.cc",
"mac/process_snapshot_mac.h",
"mac/process_types.cc",
"mac/process_types.h",
"mac/process_types/custom.cc",
"mac/process_types/flavors.h",
"mac/process_types/internal.h",
"mac/process_types/traits.h",
"mac/system_snapshot_mac.cc",
"mac/system_snapshot_mac.h",
"mac/thread_snapshot_mac.cc",
"mac/thread_snapshot_mac.h",
]
}
[ios] Bring up first draft process and module snapshot. Gather most of the necessary information for the module snapshot. Note that: - The 'capture' portion of this CL will be moved out of the snapshot interface and into a separate in-process dump to disk location. - All of the pointer dereferences need to be wrapped in vm_read. - The read-fast-and-dump logic in module_snapshot may end up in a different file completely, but until we pick a serialization/deserialization method, keep it in module_snapshot_ios. Change-Id: Ie80c739c167634520d13ec920a29a80116aa3bfe Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2079196 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Justin Cohen <justincohen@chromium.org>
2020-03-04 15:19:46 -05:00
if (crashpad_is_ios) {
sources += [
ios: Migrate ios/snapshot to reading intermediate dumps. Change-Id: Ib7715e642fa685a5f607239d07dcb68868cacb09 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2883523 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2021-05-26 15:12:33 -04:00
"ios/exception_snapshot_ios_intermediate_dump.cc",
"ios/exception_snapshot_ios_intermediate_dump.h",
"ios/intermediate_dump_reader_util.cc",
"ios/intermediate_dump_reader_util.h",
"ios/memory_snapshot_ios_intermediate_dump.cc",
"ios/memory_snapshot_ios_intermediate_dump.h",
"ios/module_snapshot_ios_intermediate_dump.cc",
"ios/module_snapshot_ios_intermediate_dump.h",
"ios/process_snapshot_ios_intermediate_dump.cc",
"ios/process_snapshot_ios_intermediate_dump.h",
"ios/system_snapshot_ios_intermediate_dump.cc",
"ios/system_snapshot_ios_intermediate_dump.h",
"ios/thread_snapshot_ios_intermediate_dump.cc",
"ios/thread_snapshot_ios_intermediate_dump.h",
[ios] Bring up first draft thread and memory snapshot. Gather most of the necessary information for the thread snapshot. Note that: - The 'capture' portion of this CL will be moved out of the snapshot interface and into a separate in-process dump to disk location. - All of the pointer dereferences need to be wrapped in vm_read. - The read-fast-and-dump logic in thread_snapshot may end up in a different file completely, but until we pick a serialization/deserialization method, keep it as-is. Change-Id: I80ba323cb6a59ac0dd1bba9150d047ba83cc4dad Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2085572 Reviewed-by: Mark Mentovai <mark@chromium.org> Reviewed-by: Justin Cohen <justincohen@chromium.org>
2020-03-20 10:37:01 -04:00
"mac/cpu_context_mac.cc",
"mac/cpu_context_mac.h",
[ios] Bring up first draft process and module snapshot. Gather most of the necessary information for the module snapshot. Note that: - The 'capture' portion of this CL will be moved out of the snapshot interface and into a separate in-process dump to disk location. - All of the pointer dereferences need to be wrapped in vm_read. - The read-fast-and-dump logic in module_snapshot may end up in a different file completely, but until we pick a serialization/deserialization method, keep it in module_snapshot_ios. Change-Id: Ie80c739c167634520d13ec920a29a80116aa3bfe Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2079196 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Justin Cohen <justincohen@chromium.org>
2020-03-04 15:19:46 -05:00
]
}
gn, android: Build for Android with GN With a companion mini_chromium change at https://crrev.com/c/841203, it’s possible to configure via “gn args” as follows: android_ndk = "/android/android-ndk-r16" target_cpu = "x86_64" target_os = "android" Note that a standalone toolchain is not required. Bug: crashpad:30, crashpad:79 Change-Id: Ica55bdcb82c730909c05dd9fecb40a74eca78c8a Reviewed-on: https://chromium-review.googlesource.com/841286 Reviewed-by: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org>
2017-12-21 17:54:12 -05:00
if (crashpad_is_linux || crashpad_is_android) {
gn, linux: Build for Linux with GN This is sufficient for a native Linux build using GN. Android is not yet supported. mini_chromium side: https://crrev.com/c/833407 This also updates mini_chromium to 404f6dbf9928. c913ef97a236 gn, linux: Build for Linux with GN 404f6dbf9928 gn: Don’t use .rsp files; rationalize descriptions and output dirs Bug: crashpad:79 Change-Id: I4f3b72fd02884d77812e520fb95231b35815677d Reviewed-on: https://chromium-review.googlesource.com/833408 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-12-19 14:21:14 -05:00
sources += [
Linux: capture memory pointed to by context This adds support for capturing memory snippets for addresses currently stored in registers to Linux/Android/CrOS. Modeled after the existing support on Windows. Bug: crashpad:30 Change-Id: Ib7cb523555a6e8e4d70145c205d67dcfbc9c7fcc Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3273712 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2021-11-12 18:55:21 +01:00
"linux/capture_memory_delegate_linux.cc",
"linux/capture_memory_delegate_linux.h",
gn, linux: Build for Linux with GN This is sufficient for a native Linux build using GN. Android is not yet supported. mini_chromium side: https://crrev.com/c/833407 This also updates mini_chromium to 404f6dbf9928. c913ef97a236 gn, linux: Build for Linux with GN 404f6dbf9928 gn: Don’t use .rsp files; rationalize descriptions and output dirs Bug: crashpad:79 Change-Id: I4f3b72fd02884d77812e520fb95231b35815677d Reviewed-on: https://chromium-review.googlesource.com/833408 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-12-19 14:21:14 -05:00
"linux/cpu_context_linux.cc",
"linux/cpu_context_linux.h",
"linux/debug_rendezvous.cc",
"linux/debug_rendezvous.h",
"linux/exception_snapshot_linux.cc",
"linux/exception_snapshot_linux.h",
Rename ProcessReader to platform-suffixed versions Mac's ProcessReader becomes ProcessReaderMac. Linux/Android's ProcessReader becomes ProcessReaderLinux. Fuchsia's ProcessReader becomes ProcessReaderFuchsia. No intended change in behavior. Bug: crashpad:196, crashpad:30 Change-Id: I7ec8d72f79533bd78189173261ade2ad99010bad Reviewed-on: https://chromium-review.googlesource.com/930321 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2018-02-22 12:12:26 -08:00
"linux/process_reader_linux.cc",
"linux/process_reader_linux.h",
gn, linux: Build for Linux with GN This is sufficient for a native Linux build using GN. Android is not yet supported. mini_chromium side: https://crrev.com/c/833407 This also updates mini_chromium to 404f6dbf9928. c913ef97a236 gn, linux: Build for Linux with GN 404f6dbf9928 gn: Don’t use .rsp files; rationalize descriptions and output dirs Bug: crashpad:79 Change-Id: I4f3b72fd02884d77812e520fb95231b35815677d Reviewed-on: https://chromium-review.googlesource.com/833408 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-12-19 14:21:14 -05:00
"linux/process_snapshot_linux.cc",
"linux/process_snapshot_linux.h",
"linux/signal_context.h",
"linux/system_snapshot_linux.cc",
"linux/system_snapshot_linux.h",
"linux/thread_snapshot_linux.cc",
"linux/thread_snapshot_linux.h",
Add ProcessSnapshotSanitized A ProcessSnapshotSanitized enables filtering possibly sensitive information from a snapshot. WebView has different privacy constraints than Chrome and needs to avoid collecting data in annotations or from stack memory that may contain PII. This CL enables: 1. Filtering annotations by name using a whitelist. 2. Filtering for crashes which reference a particular module. 3. Redacting non-essential information from stack memory. This CL does not provide a client interface to enable sanitization. Bug: crashpad:30 Change-Id: I8944c70fdcca6d6d4b7955d983320909bf871254 Reviewed-on: https://chromium-review.googlesource.com/1070472 Commit-Queue: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org>
2018-06-11 09:38:24 -07:00
"sanitized/memory_snapshot_sanitized.cc",
"sanitized/memory_snapshot_sanitized.h",
"sanitized/module_snapshot_sanitized.cc",
"sanitized/module_snapshot_sanitized.h",
"sanitized/process_snapshot_sanitized.cc",
"sanitized/process_snapshot_sanitized.h",
android/linux: add a client interface to control sanitization Sanitization is controlled by a SanitizationInformation struct to be read from the client's memory. The address of this struct is either passed in a ClientInformation when the client requests a crash dump, or as a flag to the handler --sanitization_information. Bug: crashpad:30 Change-Id: I2744f8fb85b4fea7362b2b88faa4bef1da74e36b Reviewed-on: https://chromium-review.googlesource.com/1083143 Commit-Queue: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org>
2018-06-12 08:30:36 -07:00
"sanitized/sanitization_information.cc",
"sanitized/sanitization_information.h",
Add ProcessSnapshotSanitized A ProcessSnapshotSanitized enables filtering possibly sensitive information from a snapshot. WebView has different privacy constraints than Chrome and needs to avoid collecting data in annotations or from stack memory that may contain PII. This CL enables: 1. Filtering annotations by name using a whitelist. 2. Filtering for crashes which reference a particular module. 3. Redacting non-essential information from stack memory. This CL does not provide a client interface to enable sanitization. Bug: crashpad:30 Change-Id: I8944c70fdcca6d6d4b7955d983320909bf871254 Reviewed-on: https://chromium-review.googlesource.com/1070472 Commit-Queue: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org>
2018-06-11 09:38:24 -07:00
"sanitized/thread_snapshot_sanitized.cc",
"sanitized/thread_snapshot_sanitized.h",
gn, linux: Build for Linux with GN This is sufficient for a native Linux build using GN. Android is not yet supported. mini_chromium side: https://crrev.com/c/833407 This also updates mini_chromium to 404f6dbf9928. c913ef97a236 gn, linux: Build for Linux with GN 404f6dbf9928 gn: Don’t use .rsp files; rationalize descriptions and output dirs Bug: crashpad:79 Change-Id: I4f3b72fd02884d77812e520fb95231b35815677d Reviewed-on: https://chromium-review.googlesource.com/833408 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-12-19 14:21:14 -05:00
]
}
Use CrashpadInfoReader in ModuleSnapshotWin In preparation for deleting the custom CrashpadInfo reading routines in the PEImageReader and also deleting the PEImageAnnotationsReader, this change moves ModuleSnapshotWin to using the platform-independent CrashpadInfoReader. Bug: crashpad:270 Change-Id: Idad5de173200068243eacb2bb11b2d95b6438e90 Reviewed-on: https://chromium-review.googlesource.com/c/1388017 Commit-Queue: Vlad Tsyrklevich <vtsyrklevich@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-12-21 13:42:51 -08:00
if (crashpad_is_linux || crashpad_is_android || crashpad_is_fuchsia ||
crashpad_is_win) {
fuchsia: Get CrashpadInfoReader working Bug: crashpad:196 Change-Id: Ia9bcc45891fd5cf40cccc655c4b904b1610e5932 Reviewed-on: https://chromium-review.googlesource.com/875117 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-01-18 14:34:41 -08:00
sources += [
"crashpad_types/crashpad_info_reader.cc",
"crashpad_types/crashpad_info_reader.h",
Use CrashpadInfoReader in ModuleSnapshotWin In preparation for deleting the custom CrashpadInfo reading routines in the PEImageReader and also deleting the PEImageAnnotationsReader, this change moves ModuleSnapshotWin to using the platform-independent CrashpadInfoReader. Bug: crashpad:270 Change-Id: Idad5de173200068243eacb2bb11b2d95b6438e90 Reviewed-on: https://chromium-review.googlesource.com/c/1388017 Commit-Queue: Vlad Tsyrklevich <vtsyrklevich@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-12-21 13:42:51 -08:00
]
}
if (crashpad_is_linux || crashpad_is_android || crashpad_is_fuchsia) {
sources += [
fuchsia: Make ImageAnnotationReader[Test] work Ports the test away from fork() to MultiprocessExec. Requires a Fuchsia SDK that includes the fix in https://fuchsia-review.googlesource.com/c/zircon/+/125081. Bug: crashpad:196, crashpad:215 Change-Id: Ia8d382cebe8d2ffc8d877e5249baf0e58aee248c Reviewed-on: https://chromium-review.googlesource.com/927355 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-02-20 16:10:20 -08:00
"crashpad_types/image_annotation_reader.cc",
"crashpad_types/image_annotation_reader.h",
fuchsia: Port ElfImageReader and (some of) its tests (Still need to avoid fork()-dependence for the non-self tests.) Bug: crashpad:196 Change-Id: Ib34fe33c7ec295881c1f555995072d9ff742647f Reviewed-on: https://chromium-review.googlesource.com/876650 Reviewed-by: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2018-01-19 14:03:34 -08:00
"elf/elf_dynamic_array_reader.cc",
"elf/elf_dynamic_array_reader.h",
"elf/elf_image_reader.cc",
"elf/elf_image_reader.h",
"elf/elf_symbol_table_reader.cc",
"elf/elf_symbol_table_reader.h",
Refactor ModuleSnapshot(Linux|Fuchsia) into ModuleSnapshotElf They were largely the same after recent changes, so with a bit at initialization time the whole class can be de-duplicated. Bug: crashpad:196, crashpad:30 Change-Id: I2f5df797dfe36e120090e570273b48ee03f660a5 Reviewed-on: https://chromium-review.googlesource.com/927611 Reviewed-by: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2018-02-20 16:11:41 -08:00
"elf/module_snapshot_elf.cc",
"elf/module_snapshot_elf.h",
fuchsia: Get CrashpadInfoReader working Bug: crashpad:196 Change-Id: Ia9bcc45891fd5cf40cccc655c4b904b1610e5932 Reviewed-on: https://chromium-review.googlesource.com/875117 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-01-18 14:34:41 -08:00
]
}
gn: Avoid depending on BUILDCONFIG.gn globals Goes with https://chromium-review.googlesource.com/c/chromium/mini_chromium/+/834648. Includes mini_chromium DEPS roll to pull in https://chromium.googlesource.com/chromium/mini_chromium/+/edfe51ce818e55eae73ab3f144a360e855533888 Bug: crashpad:79, crashpad:196 Change-Id: Ib45cc738aecf9ae727f8faeff81f3b71e2dc9de8 Reviewed-on: https://chromium-review.googlesource.com/834543 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2017-12-19 15:31:04 -08:00
if (crashpad_is_win) {
gn: Move sources out to explicit blocks This avoids relying on set_sources_assignment_filter, and so gets closer to a correct set of files to build on Fuchsia. Bug: crashpad:79, crashpad:196 Change-Id: Ib7daa5137935113c6645b72eb1dedd943a9db96e Reviewed-on: https://chromium-review.googlesource.com/797672 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-29 11:59:18 -08:00
sources += [
"win/capture_memory_delegate_win.cc",
"win/capture_memory_delegate_win.h",
"win/cpu_context_win.cc",
"win/cpu_context_win.h",
"win/exception_snapshot_win.cc",
"win/exception_snapshot_win.h",
"win/memory_map_region_snapshot_win.cc",
"win/memory_map_region_snapshot_win.h",
"win/module_snapshot_win.cc",
"win/module_snapshot_win.h",
"win/pe_image_annotations_reader.cc",
"win/pe_image_annotations_reader.h",
"win/pe_image_reader.cc",
"win/pe_image_reader.h",
"win/pe_image_resource_reader.cc",
"win/pe_image_resource_reader.h",
"win/process_reader_win.cc",
"win/process_reader_win.h",
"win/process_snapshot_win.cc",
"win/process_snapshot_win.h",
"win/process_subrange_reader.cc",
"win/process_subrange_reader.h",
"win/system_snapshot_win.cc",
"win/system_snapshot_win.h",
"win/thread_snapshot_win.cc",
"win/thread_snapshot_win.h",
]
}
gn: Avoid depending on BUILDCONFIG.gn globals Goes with https://chromium-review.googlesource.com/c/chromium/mini_chromium/+/834648. Includes mini_chromium DEPS roll to pull in https://chromium.googlesource.com/chromium/mini_chromium/+/edfe51ce818e55eae73ab3f144a360e855533888 Bug: crashpad:79, crashpad:196 Change-Id: Ib45cc738aecf9ae727f8faeff81f3b71e2dc9de8 Reviewed-on: https://chromium-review.googlesource.com/834543 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2017-12-19 15:31:04 -08:00
if (crashpad_is_fuchsia) {
fuchsia: Get crashpad_snapshot_test building ProcessSnapshotFuchsia is just a stub, so running fails immediately. Bug: crashpad:196 Change-Id: Ie281cc13c4ff4a6e9699e882dbd6207daaab346d Reviewed-on: https://chromium-review.googlesource.com/809234 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-12-05 15:43:23 -08:00
sources += [
fuchsia: Capture general purpose registers in thread snapshot Conversion to CPUContext is currently only implemented for x64. Bug: crashpad:196 Change-Id: I3fb8541f70a6f8d6f12c02e6b17c78e07e195056 Reviewed-on: https://chromium-review.googlesource.com/1007967 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2018-04-12 14:16:10 -07:00
"fuchsia/cpu_context_fuchsia.cc",
"fuchsia/cpu_context_fuchsia.h",
fuchsia: Add implementation of ExceptionSnapshot Bug: crashpad:196 Change-Id: I5aea3484c185096898bafe847c83474a91f5d8c7 Reviewed-on: https://chromium-review.googlesource.com/1038128 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2018-05-03 13:31:48 -07:00
"fuchsia/exception_snapshot_fuchsia.cc",
"fuchsia/exception_snapshot_fuchsia.h",
fuchsia: Identify and include stack mapping in dump Bug: crashpad:196 Change-Id: I4d71502028ba1d961e53c0450c3ae88c6285f04e Reviewed-on: https://chromium-review.googlesource.com/1033358 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2018-04-30 12:57:03 -07:00
"fuchsia/memory_map_fuchsia.cc",
"fuchsia/memory_map_fuchsia.h",
fuchsia: Include address space information in process snapshot This plumbs some of the ZX_INFO_PROCESS_MAPS information out into MINIDUMP_MEMORY_INFO. The mapping loses some information that Zircon provides, and some of the data that Windows would provide isn't available (for example, AllocationProtect). But this gives a general idea of the memory layout of the process to check for bad pointers, etc. when inspecting crashes. Bug: fuchsia:DX-615 Change-Id: I2d7c02be0996672253cf0b1eb6a60b0a55e6033b Reviewed-on: https://chromium-review.googlesource.com/c/1377089 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-12-14 13:17:43 -08:00
"fuchsia/memory_map_region_snapshot_fuchsia.cc",
"fuchsia/memory_map_region_snapshot_fuchsia.h",
Rename ProcessReader to platform-suffixed versions Mac's ProcessReader becomes ProcessReaderMac. Linux/Android's ProcessReader becomes ProcessReaderLinux. Fuchsia's ProcessReader becomes ProcessReaderFuchsia. No intended change in behavior. Bug: crashpad:196, crashpad:30 Change-Id: I7ec8d72f79533bd78189173261ade2ad99010bad Reviewed-on: https://chromium-review.googlesource.com/930321 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2018-02-22 12:12:26 -08:00
"fuchsia/process_reader_fuchsia.cc",
"fuchsia/process_reader_fuchsia.h",
fuchsia: Get crashpad_snapshot_test building ProcessSnapshotFuchsia is just a stub, so running fails immediately. Bug: crashpad:196 Change-Id: Ie281cc13c4ff4a6e9699e882dbd6207daaab346d Reviewed-on: https://chromium-review.googlesource.com/809234 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-12-05 15:43:23 -08:00
"fuchsia/process_snapshot_fuchsia.cc",
"fuchsia/process_snapshot_fuchsia.h",
fuchsia: Implementation of system snapshot Mostly sensible implementation for x64 via cpuid. It's too early for Fuchsia to have a version number, so nothing is reported for those fields. ARM64 isn't implemented at all and would hit a lot of NOTREACHED()s. Bug: crashpad:196 Change-Id: I6ca8b12e16fe0cf773a17c88ca9d407b028a501c Reviewed-on: https://chromium-review.googlesource.com/1005906 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2018-04-10 15:34:33 -07:00
"fuchsia/system_snapshot_fuchsia.cc",
"fuchsia/system_snapshot_fuchsia.h",
fuchsia: Add implementation of ThreadSnapshot This is mostly empty except for the ID, until I concoct a way to get the stack out of Fuchsia, and implement context capture. Bug: crashpad:196 Change-Id: I26d0622d44aefba88750f7ec6feb1a6e95467208 Reviewed-on: https://chromium-review.googlesource.com/932941 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2018-02-22 16:48:50 -08:00
"fuchsia/thread_snapshot_fuchsia.cc",
"fuchsia/thread_snapshot_fuchsia.h",
fuchsia: Get crashpad_snapshot_test building ProcessSnapshotFuchsia is just a stub, so running fails immediately. Bug: crashpad:196 Change-Id: Ie281cc13c4ff4a6e9699e882dbd6207daaab346d Reviewed-on: https://chromium-review.googlesource.com/809234 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-12-05 15:43:23 -08:00
]
}
mac-arm64: Allow target_cpu = "mac_universal" to create universal builds When building for macOS and configured with target_cpu = "mac_universal", bi-architecture x86_64/arm64 output will be produced. mac_universal is, so far, a “Crashpad special” that will only work with mini_chromium and the standalone Crashpad build, and not the in-Chromium build. It exists to support Keystone, which intends to ship as x86_64/arm64 universal. Includes: Update mini_chromium to e0008f2714a76c7f2a3854fa75774427a886d6b9 e0008f2714a7 mac-arm64: Allow target_cpu = "mac_universal" to create universal builds Bug: crashpad:345 Change-Id: I5ff2dce5ffae58186e33757aa94587f8eca20b99 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2387410 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org>
2020-09-02 16:42:59 -04:00
if (current_cpu == "x86" || current_cpu == "x64" ||
(crashpad_is_mac && current_cpu == "mac_universal")) {
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
sources += [
"x86/cpuid_reader.cc",
"x86/cpuid_reader.h",
]
}
Rework GN files to start to support building standalone, and also in Chromium - Adds a .gn and a build/BUILDCONFIG.gn that uses mini_chromium's build/BUILD.gn. - Adds some stub BUILD.gn files in locations where Chromium expects them (in //build, //testing, //third_party) containing empty targets/configs. These are no-ops in standalone builds, but add functionality when building in Chromium. This is in preference to having a global bool that conditionally does Chromium-y things in the Crashpad build files. These stub files are all contained in a secondary source root in build/chromium_compatibility, referred to by //.gn. - Adds //base/BUILD.gn which forwards to mini_chromium/base. This is only used when building standalone so that both Chromium and Crashpad can refer to it as "//base". - Changes references to other Crashpad targets to be relatively specified so that they work when the root of the project is //, and also when it's //third_party/crashpad/crashpad as it is in Chromium. - Moves any error-causing Mac/Win-specific files into explicit if (is_mac) or if (is_win) blocks as part of removing the dependency on set_sources_assignment_filter(). As yet unresolved: - CRASHPAD_IN_CHROMIUM needs to be removed when standalone; to be tackled in a follow up. - Not sure what to do with zlib yet, the build file currently assumes "in Chromium" too, and similarly having Crashpad //third_party/zlib:zlib pointing at itself doesn't work. Bug: crashpad:79 Change-Id: I6a7dda214e4b3b14a60c1ed285267ab97432a1a8 Reviewed-on: https://chromium-review.googlesource.com/777410 Reviewed-by: Mark Mentovai <mark@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-28 10:31:13 -08:00
public_configs = [ "..:crashpad_config" ]
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
Make “gn check” pass Change-Id: Ia7a215e1a2d0a3b1868b00c5d47b46ef8a675cdc Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2144917 Reviewed-by: Justin Cohen <justincohen@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org> Commit-Queue: Mark Mentovai <mark@chromium.org>
2020-04-10 17:40:41 -04:00
public_deps = [ ":context" ]
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
deps = [
ios: Update XCUITests to check various crash type exception codes. Bug: crashpad:31 Change-Id: I804def3be0050b3e6f15d7d77d0b70184c380673 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3087722 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2021-10-28 17:02:27 -04:00
"$mini_chromium_source_parent:base",
ios: Extract common targets to be shared for iOS. Move some common files out of client and handler for iOS usage. Bug: crashpad: 31 Change-Id: I1933eaaa7580a81017c52b77dfb636a8fa31ee78 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2851059 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Justin Cohen <justincohen@chromium.org>
2021-04-27 21:27:09 -04:00
"../client:common",
Rework GN files to start to support building standalone, and also in Chromium - Adds a .gn and a build/BUILDCONFIG.gn that uses mini_chromium's build/BUILD.gn. - Adds some stub BUILD.gn files in locations where Chromium expects them (in //build, //testing, //third_party) containing empty targets/configs. These are no-ops in standalone builds, but add functionality when building in Chromium. This is in preference to having a global bool that conditionally does Chromium-y things in the Crashpad build files. These stub files are all contained in a secondary source root in build/chromium_compatibility, referred to by //.gn. - Adds //base/BUILD.gn which forwards to mini_chromium/base. This is only used when building standalone so that both Chromium and Crashpad can refer to it as "//base". - Changes references to other Crashpad targets to be relatively specified so that they work when the root of the project is //, and also when it's //third_party/crashpad/crashpad as it is in Chromium. - Moves any error-causing Mac/Win-specific files into explicit if (is_mac) or if (is_win) blocks as part of removing the dependency on set_sources_assignment_filter(). As yet unresolved: - CRASHPAD_IN_CHROMIUM needs to be removed when standalone; to be tackled in a follow up. - Not sure what to do with zlib yet, the build file currently assumes "in Chromium" too, and similarly having Crashpad //third_party/zlib:zlib pointing at itself doesn't work. Bug: crashpad:79 Change-Id: I6a7dda214e4b3b14a60c1ed285267ab97432a1a8 Reviewed-on: https://chromium-review.googlesource.com/777410 Reviewed-by: Mark Mentovai <mark@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-28 10:31:13 -08:00
"../compat",
Make “gn check” pass Change-Id: Ia7a215e1a2d0a3b1868b00c5d47b46ef8a675cdc Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2144917 Reviewed-by: Justin Cohen <justincohen@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org> Commit-Queue: Mark Mentovai <mark@chromium.org>
2020-04-10 17:40:41 -04:00
"../minidump:format",
Rework GN files to start to support building standalone, and also in Chromium - Adds a .gn and a build/BUILDCONFIG.gn that uses mini_chromium's build/BUILD.gn. - Adds some stub BUILD.gn files in locations where Chromium expects them (in //build, //testing, //third_party) containing empty targets/configs. These are no-ops in standalone builds, but add functionality when building in Chromium. This is in preference to having a global bool that conditionally does Chromium-y things in the Crashpad build files. These stub files are all contained in a secondary source root in build/chromium_compatibility, referred to by //.gn. - Adds //base/BUILD.gn which forwards to mini_chromium/base. This is only used when building standalone so that both Chromium and Crashpad can refer to it as "//base". - Changes references to other Crashpad targets to be relatively specified so that they work when the root of the project is //, and also when it's //third_party/crashpad/crashpad as it is in Chromium. - Moves any error-causing Mac/Win-specific files into explicit if (is_mac) or if (is_win) blocks as part of removing the dependency on set_sources_assignment_filter(). As yet unresolved: - CRASHPAD_IN_CHROMIUM needs to be removed when standalone; to be tackled in a follow up. - Not sure what to do with zlib yet, the build file currently assumes "in Chromium" too, and similarly having Crashpad //third_party/zlib:zlib pointing at itself doesn't work. Bug: crashpad:79 Change-Id: I6a7dda214e4b3b14a60c1ed285267ab97432a1a8 Reviewed-on: https://chromium-review.googlesource.com/777410 Reviewed-by: Mark Mentovai <mark@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-28 10:31:13 -08:00
"../util",
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
]
gn: Avoid depending on BUILDCONFIG.gn globals Goes with https://chromium-review.googlesource.com/c/chromium/mini_chromium/+/834648. Includes mini_chromium DEPS roll to pull in https://chromium.googlesource.com/chromium/mini_chromium/+/edfe51ce818e55eae73ab3f144a360e855533888 Bug: crashpad:79, crashpad:196 Change-Id: Ib45cc738aecf9ae727f8faeff81f3b71e2dc9de8 Reviewed-on: https://chromium-review.googlesource.com/834543 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2017-12-19 15:31:04 -08:00
if (crashpad_is_win) {
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
cflags = [ "/wd4201" ] # nonstandard extension used : nameless struct/union
libs = [ "powrprof.lib" ]
}
}
Make “gn check” pass Change-Id: Ia7a215e1a2d0a3b1868b00c5d47b46ef8a675cdc Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2144917 Reviewed-by: Justin Cohen <justincohen@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org> Commit-Queue: Mark Mentovai <mark@chromium.org>
2020-04-10 17:40:41 -04:00
# :context is the only part of snapshot that minidump may depend on.
static_library("context") {
sources = [
"cpu_architecture.h",
"cpu_context.cc",
"cpu_context.h",
]
public_configs = [ "..:crashpad_config" ]
deps = [
[third_party] Make mini_chromium relocatable This will accommodate moving third_party/mini_chromium around. The default location is unchanged for now. There are GN variables that may need to be updated when Fuchsia's source re-organizes its layout: * mini_chromium_source_parent : this contains a BUILD.gn with groups and encloses the mini_chromium_source_root. This is controlled by the structure of the project that depends on this project. * _mini_chromium_source_root : this is what is normally checked out from git, the upstream source directory * mini_chromium_import_root : points inside source_root to make GN files accessible. This first step breaks out case logic for "if (crashpad_is_in_fuchsia)" even if the value is unchanged for now. This will faciliate a smaller change when Fuchsia re-structures third_party sources. Change-Id: I09e5362f4be8fdb440e3891422881b1053052341 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3062424 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Mark Mentovai <mark@chromium.org>
2021-07-28 23:57:54 +00:00
"$mini_chromium_source_parent:base",
Make “gn check” pass Change-Id: Ia7a215e1a2d0a3b1868b00c5d47b46ef8a675cdc Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2144917 Reviewed-by: Justin Cohen <justincohen@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org> Commit-Queue: Mark Mentovai <mark@chromium.org>
2020-04-10 17:40:41 -04:00
"../util",
]
if (crashpad_is_win) {
cflags = [ "/wd4201" ] # nonstandard extension used : nameless struct/union
}
}
[libFuzzer] Enable fuzz targets to build in Chromium Enable building elf_image_reader_fuzzer in Chromium. Rename it to crashpad_elf_image_reader_fuzzer so that its clearer where the fuzzer comes from. Import chromium's fuzzer_test definition when building in Chromium and make sure fuzzer is only built on Linux since it breaks fuzzer build on Win (and maybe Mac?). Bug: 950093 Change-Id: I8afc104d26871311b04931b82a1600614a81bfc8 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/1597091 Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2019-05-06 12:01:34 -07:00
if (crashpad_is_linux) {
crashpad_fuzzer_test("elf_image_reader_fuzzer") {
Reformat all gn files Port of chromium-side https://chromium-review.googlesource.com/c/chromium/src/+/1997899 Bug: chromium:1041419 Change-Id: Ic7afefa0dea024da37fe4bb0f965840a160e2166 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2015428 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2020-01-23 08:00:33 -05:00
sources = [ "elf/elf_image_reader_fuzzer.cc" ]
Add libfuzzer support Adds the build support for using libfuzzer controlled by setting `crashpad_use_libfuzzer=true`. Also adds a first fuzzer (for ElfImageReader). Currently only runs on Linux, but should work on Fuchsia too with some minor fixes (not sure yet whether the fixes required are toolchain or in our build setup). Run as: out/lin/elf_image_reader_fuzzer snapshot/elf/elf_image_reader_fuzzer_corpus/ hits an OOM pretty quickly in trying to allocate a giant buffer. Bug: crashpad:30, crashpad:196, crashpad:233 Change-Id: Idd3ca11fe00319b8b29e029d5e13b17bfd518ea0 Reviewed-on: https://chromium-review.googlesource.com/1083451 Reviewed-by: Robert Sesek <rsesek@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2018-06-04 16:16:19 -07:00
[libFuzzer] Enable fuzz targets to build in Chromium Enable building elf_image_reader_fuzzer in Chromium. Rename it to crashpad_elf_image_reader_fuzzer so that its clearer where the fuzzer comes from. Import chromium's fuzzer_test definition when building in Chromium and make sure fuzzer is only built on Linux since it breaks fuzzer build on Win (and maybe Mac?). Bug: 950093 Change-Id: I8afc104d26871311b04931b82a1600614a81bfc8 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/1597091 Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2019-05-06 12:01:34 -07:00
deps = [
":snapshot",
[third_party] Make mini_chromium relocatable This will accommodate moving third_party/mini_chromium around. The default location is unchanged for now. There are GN variables that may need to be updated when Fuchsia's source re-organizes its layout: * mini_chromium_source_parent : this contains a BUILD.gn with groups and encloses the mini_chromium_source_root. This is controlled by the structure of the project that depends on this project. * _mini_chromium_source_root : this is what is normally checked out from git, the upstream source directory * mini_chromium_import_root : points inside source_root to make GN files accessible. This first step breaks out case logic for "if (crashpad_is_in_fuchsia)" even if the value is unchanged for now. This will faciliate a smaller change when Fuchsia re-structures third_party sources. Change-Id: I09e5362f4be8fdb440e3891422881b1053052341 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3062424 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Mark Mentovai <mark@chromium.org>
2021-07-28 23:57:54 +00:00
"$mini_chromium_source_parent:base",
Add missing dependency on util to fuzzer This makes it possible to run gn check --deps for crashpad/snapshot in chromium. ERROR at //third_party/crashpad/crashpad/snapshot/elf/elf_image_reader_fuzzer.cc:19:11: Can't include this header from here. #include "util/process/process_memory.h" ^---------------------------- Bug: chromium:1159035 Change-Id: Idddcf95da2a349842fa86a8d595216fbca3b8822 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2676581 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2021-02-04 19:34:27 +01:00
"../util:util",
[libFuzzer] Enable fuzz targets to build in Chromium Enable building elf_image_reader_fuzzer in Chromium. Rename it to crashpad_elf_image_reader_fuzzer so that its clearer where the fuzzer comes from. Import chromium's fuzzer_test definition when building in Chromium and make sure fuzzer is only built on Linux since it breaks fuzzer build on Win (and maybe Mac?). Bug: 950093 Change-Id: I8afc104d26871311b04931b82a1600614a81bfc8 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/1597091 Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2019-05-06 12:01:34 -07:00
]
seed_corpus = "elf/elf_image_reader_fuzzer_corpus"
}
Add libfuzzer support Adds the build support for using libfuzzer controlled by setting `crashpad_use_libfuzzer=true`. Also adds a first fuzzer (for ElfImageReader). Currently only runs on Linux, but should work on Fuchsia too with some minor fixes (not sure yet whether the fixes required are toolchain or in our build setup). Run as: out/lin/elf_image_reader_fuzzer snapshot/elf/elf_image_reader_fuzzer_corpus/ hits an OOM pretty quickly in trying to allocate a giant buffer. Bug: crashpad:30, crashpad:196, crashpad:233 Change-Id: Idd3ca11fe00319b8b29e029d5e13b17bfd518ea0 Reviewed-on: https://chromium-review.googlesource.com/1083451 Reviewed-by: Robert Sesek <rsesek@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2018-06-04 16:16:19 -07:00
}
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
static_library("test_support") {
testonly = true
sources = [
"test/test_cpu_context.cc",
"test/test_cpu_context.h",
"test/test_exception_snapshot.cc",
"test/test_exception_snapshot.h",
"test/test_memory_map_region_snapshot.cc",
"test/test_memory_map_region_snapshot.h",
"test/test_memory_snapshot.cc",
"test/test_memory_snapshot.h",
"test/test_module_snapshot.cc",
"test/test_module_snapshot.h",
"test/test_process_snapshot.cc",
"test/test_process_snapshot.h",
"test/test_system_snapshot.cc",
"test/test_system_snapshot.h",
"test/test_thread_snapshot.cc",
"test/test_thread_snapshot.h",
]
Rework GN files to start to support building standalone, and also in Chromium - Adds a .gn and a build/BUILDCONFIG.gn that uses mini_chromium's build/BUILD.gn. - Adds some stub BUILD.gn files in locations where Chromium expects them (in //build, //testing, //third_party) containing empty targets/configs. These are no-ops in standalone builds, but add functionality when building in Chromium. This is in preference to having a global bool that conditionally does Chromium-y things in the Crashpad build files. These stub files are all contained in a secondary source root in build/chromium_compatibility, referred to by //.gn. - Adds //base/BUILD.gn which forwards to mini_chromium/base. This is only used when building standalone so that both Chromium and Crashpad can refer to it as "//base". - Changes references to other Crashpad targets to be relatively specified so that they work when the root of the project is //, and also when it's //third_party/crashpad/crashpad as it is in Chromium. - Moves any error-causing Mac/Win-specific files into explicit if (is_mac) or if (is_win) blocks as part of removing the dependency on set_sources_assignment_filter(). As yet unresolved: - CRASHPAD_IN_CHROMIUM needs to be removed when standalone; to be tackled in a follow up. - Not sure what to do with zlib yet, the build file currently assumes "in Chromium" too, and similarly having Crashpad //third_party/zlib:zlib pointing at itself doesn't work. Bug: crashpad:79 Change-Id: I6a7dda214e4b3b14a60c1ed285267ab97432a1a8 Reviewed-on: https://chromium-review.googlesource.com/777410 Reviewed-by: Mark Mentovai <mark@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-28 10:31:13 -08:00
public_configs = [ "..:crashpad_config" ]
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
Reformat all gn files Port of chromium-side https://chromium-review.googlesource.com/c/chromium/src/+/1997899 Bug: chromium:1041419 Change-Id: Ic7afefa0dea024da37fe4bb0f965840a160e2166 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2015428 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2020-01-23 08:00:33 -05:00
public_deps = [ ":snapshot" ]
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
deps = [
[third_party] Make mini_chromium relocatable This will accommodate moving third_party/mini_chromium around. The default location is unchanged for now. There are GN variables that may need to be updated when Fuchsia's source re-organizes its layout: * mini_chromium_source_parent : this contains a BUILD.gn with groups and encloses the mini_chromium_source_root. This is controlled by the structure of the project that depends on this project. * _mini_chromium_source_root : this is what is normally checked out from git, the upstream source directory * mini_chromium_import_root : points inside source_root to make GN files accessible. This first step breaks out case logic for "if (crashpad_is_in_fuchsia)" even if the value is unchanged for now. This will faciliate a smaller change when Fuchsia re-structures third_party sources. Change-Id: I09e5362f4be8fdb440e3891422881b1053052341 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3062424 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Mark Mentovai <mark@chromium.org>
2021-07-28 23:57:54 +00:00
"$mini_chromium_source_parent:base",
ios: Update XCUITests to check various crash type exception codes. Bug: crashpad:31 Change-Id: I804def3be0050b3e6f15d7d77d0b70184c380673 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3087722 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2021-10-28 17:02:27 -04:00
"../compat",
Rework GN files to start to support building standalone, and also in Chromium - Adds a .gn and a build/BUILDCONFIG.gn that uses mini_chromium's build/BUILD.gn. - Adds some stub BUILD.gn files in locations where Chromium expects them (in //build, //testing, //third_party) containing empty targets/configs. These are no-ops in standalone builds, but add functionality when building in Chromium. This is in preference to having a global bool that conditionally does Chromium-y things in the Crashpad build files. These stub files are all contained in a secondary source root in build/chromium_compatibility, referred to by //.gn. - Adds //base/BUILD.gn which forwards to mini_chromium/base. This is only used when building standalone so that both Chromium and Crashpad can refer to it as "//base". - Changes references to other Crashpad targets to be relatively specified so that they work when the root of the project is //, and also when it's //third_party/crashpad/crashpad as it is in Chromium. - Moves any error-causing Mac/Win-specific files into explicit if (is_mac) or if (is_win) blocks as part of removing the dependency on set_sources_assignment_filter(). As yet unresolved: - CRASHPAD_IN_CHROMIUM needs to be removed when standalone; to be tackled in a follow up. - Not sure what to do with zlib yet, the build file currently assumes "in Chromium" too, and similarly having Crashpad //third_party/zlib:zlib pointing at itself doesn't work. Bug: crashpad:79 Change-Id: I6a7dda214e4b3b14a60c1ed285267ab97432a1a8 Reviewed-on: https://chromium-review.googlesource.com/777410 Reviewed-by: Mark Mentovai <mark@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-28 10:31:13 -08:00
"../util",
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
]
gn: Avoid depending on BUILDCONFIG.gn globals Goes with https://chromium-review.googlesource.com/c/chromium/mini_chromium/+/834648. Includes mini_chromium DEPS roll to pull in https://chromium.googlesource.com/chromium/mini_chromium/+/edfe51ce818e55eae73ab3f144a360e855533888 Bug: crashpad:79, crashpad:196 Change-Id: Ib45cc738aecf9ae727f8faeff81f3b71e2dc9de8 Reviewed-on: https://chromium-review.googlesource.com/834543 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2017-12-19 15:31:04 -08:00
if (crashpad_is_win) {
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
cflags = [ "/wd4201" ] # nonstandard extension used : nameless struct/union
}
}
gn, linux: Build for Linux with GN This is sufficient for a native Linux build using GN. Android is not yet supported. mini_chromium side: https://crrev.com/c/833407 This also updates mini_chromium to 404f6dbf9928. c913ef97a236 gn, linux: Build for Linux with GN 404f6dbf9928 gn: Don’t use .rsp files; rationalize descriptions and output dirs Bug: crashpad:79 Change-Id: I4f3b72fd02884d77812e520fb95231b35815677d Reviewed-on: https://chromium-review.googlesource.com/833408 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-12-19 14:21:14 -05:00
config("snapshot_test_link") {
visibility = [ ":*" ]
fuchsia: Port ElfImageReader and (some of) its tests (Still need to avoid fork()-dependence for the non-self tests.) Bug: crashpad:196 Change-Id: Ib34fe33c7ec295881c1f555995072d9ff742647f Reviewed-on: https://chromium-review.googlesource.com/876650 Reviewed-by: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2018-01-19 14:03:34 -08:00
if (crashpad_is_linux || crashpad_is_android || crashpad_is_fuchsia) {
gn, linux: Build for Linux with GN This is sufficient for a native Linux build using GN. Android is not yet supported. mini_chromium side: https://crrev.com/c/833407 This also updates mini_chromium to 404f6dbf9928. c913ef97a236 gn, linux: Build for Linux with GN 404f6dbf9928 gn: Don’t use .rsp files; rationalize descriptions and output dirs Bug: crashpad:79 Change-Id: I4f3b72fd02884d77812e520fb95231b35815677d Reviewed-on: https://chromium-review.googlesource.com/833408 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-12-19 14:21:14 -05:00
# There’s no way to make the link depend on this file. “inputs” doesn’t have
# the intended effect in a config. https://crbug.com/781858,
# https://crbug.com/796187.
Reformat all gn files Port of chromium-side https://chromium-review.googlesource.com/c/chromium/src/+/1997899 Bug: chromium:1041419 Change-Id: Ic7afefa0dea024da37fe4bb0f965840a160e2166 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2015428 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2020-01-23 08:00:33 -05:00
inputs = [ "elf/test_exported_symbols.sym" ]
gn, linux: Build for Linux with GN This is sufficient for a native Linux build using GN. Android is not yet supported. mini_chromium side: https://crrev.com/c/833407 This also updates mini_chromium to 404f6dbf9928. c913ef97a236 gn, linux: Build for Linux with GN 404f6dbf9928 gn: Don’t use .rsp files; rationalize descriptions and output dirs Bug: crashpad:79 Change-Id: I4f3b72fd02884d77812e520fb95231b35815677d Reviewed-on: https://chromium-review.googlesource.com/833408 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-12-19 14:21:14 -05:00
ldflags = [ "-Wl,--dynamic-list," + rebase_path(inputs[0], root_build_dir) ]
}
}
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
source_set("snapshot_test") {
testonly = true
sources = [
"cpu_context_test.cc",
Coalesce memory ranges Follows https://chromium-review.googlesource.com/c/374019/. Causes MinidumpMemoryListWriter to merge all overlapping ranges before writing the MINIDUMP_MEMORY_LIST. This is: 1) Necessary for the Google internal crash processor, which in some cases attempts to read the raw memory (displaying ASAN red zones), and aborts if there are any overlapping ranges in the minidump on load; 2) Necessary for new-ish versions of windbg (see bug 216 below). It is believed that this is a change in behavior in the tool that made dumps with overlapping ranges unreadable; 3) More efficient. The .dmp for crashy_program goes from 306K to 140K with this enabled. In Chrome minidumps where set_gather_indirectly_referenced_memory() is used (in practice this means Chrome Windows Beta, Dev, and Canary), the savings are expected to be substantial. Bug: crashpad:61, chromium:638370, crashpad:216 Change-Id: I969e1a52da555ceba59a727d933bfeef6787c7a5 Reviewed-on: https://chromium-review.googlesource.com/374539 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-02-01 15:54:56 -08:00
"memory_snapshot_test.cc",
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
"minidump/process_snapshot_minidump_test.cc",
]
gn: Avoid depending on BUILDCONFIG.gn globals Goes with https://chromium-review.googlesource.com/c/chromium/mini_chromium/+/834648. Includes mini_chromium DEPS roll to pull in https://chromium.googlesource.com/chromium/mini_chromium/+/edfe51ce818e55eae73ab3f144a360e855533888 Bug: crashpad:79, crashpad:196 Change-Id: Ib45cc738aecf9ae727f8faeff81f3b71e2dc9de8 Reviewed-on: https://chromium-review.googlesource.com/834543 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2017-12-19 15:31:04 -08:00
if (crashpad_is_mac) {
gn: Move sources out to explicit blocks This avoids relying on set_sources_assignment_filter, and so gets closer to a correct set of files to build on Fuchsia. Bug: crashpad:79, crashpad:196 Change-Id: Ib7daa5137935113c6645b72eb1dedd943a9db96e Reviewed-on: https://chromium-review.googlesource.com/797672 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-29 11:59:18 -08:00
sources += [
"mac/cpu_context_mac_test.cc",
"mac/mach_o_image_annotations_reader_test.cc",
"mac/mach_o_image_reader_test.cc",
"mac/mach_o_image_segment_reader_test.cc",
Rename ProcessReader to platform-suffixed versions Mac's ProcessReader becomes ProcessReaderMac. Linux/Android's ProcessReader becomes ProcessReaderLinux. Fuchsia's ProcessReader becomes ProcessReaderFuchsia. No intended change in behavior. Bug: crashpad:196, crashpad:30 Change-Id: I7ec8d72f79533bd78189173261ade2ad99010bad Reviewed-on: https://chromium-review.googlesource.com/930321 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2018-02-22 12:12:26 -08:00
"mac/process_reader_mac_test.cc",
gn: Move sources out to explicit blocks This avoids relying on set_sources_assignment_filter, and so gets closer to a correct set of files to build on Fuchsia. Bug: crashpad:79, crashpad:196 Change-Id: Ib7daa5137935113c6645b72eb1dedd943a9db96e Reviewed-on: https://chromium-review.googlesource.com/797672 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-29 11:59:18 -08:00
"mac/process_types_test.cc",
"mac/system_snapshot_mac_test.cc",
]
}
ios: Migrate ios/snapshot to reading intermediate dumps. Change-Id: Ib7715e642fa685a5f607239d07dcb68868cacb09 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2883523 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2021-05-26 15:12:33 -04:00
if (crashpad_is_ios) {
sources += [
ios: Add MemorySnapshotIOSIntermediateDumpTest. Change-Id: Ib8b962c631d6ae90fb1805dff5e28ab078940328 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3401570 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Justin Cohen <justincohen@chromium.org>
2022-01-22 20:57:40 -05:00
"ios/memory_snapshot_ios_intermediate_dump_test.cc",
ios: Migrate ios/snapshot to reading intermediate dumps. Change-Id: Ib7715e642fa685a5f607239d07dcb68868cacb09 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2883523 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2021-05-26 15:12:33 -04:00
"ios/process_snapshot_ios_intermediate_dump_test.cc",
"mac/cpu_context_mac_test.cc",
]
}
gn, android: Build for Android with GN With a companion mini_chromium change at https://crrev.com/c/841203, it’s possible to configure via “gn args” as follows: android_ndk = "/android/android-ndk-r16" target_cpu = "x86_64" target_os = "android" Note that a standalone toolchain is not required. Bug: crashpad:30, crashpad:79 Change-Id: Ica55bdcb82c730909c05dd9fecb40a74eca78c8a Reviewed-on: https://chromium-review.googlesource.com/841286 Reviewed-by: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org>
2017-12-21 17:54:12 -05:00
if (crashpad_is_linux || crashpad_is_android) {
gn, linux: Build for Linux with GN This is sufficient for a native Linux build using GN. Android is not yet supported. mini_chromium side: https://crrev.com/c/833407 This also updates mini_chromium to 404f6dbf9928. c913ef97a236 gn, linux: Build for Linux with GN 404f6dbf9928 gn: Don’t use .rsp files; rationalize descriptions and output dirs Bug: crashpad:79 Change-Id: I4f3b72fd02884d77812e520fb95231b35815677d Reviewed-on: https://chromium-review.googlesource.com/833408 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-12-19 14:21:14 -05:00
sources += [
"linux/debug_rendezvous_test.cc",
"linux/exception_snapshot_linux_test.cc",
Rename ProcessReader to platform-suffixed versions Mac's ProcessReader becomes ProcessReaderMac. Linux/Android's ProcessReader becomes ProcessReaderLinux. Fuchsia's ProcessReader becomes ProcessReaderFuchsia. No intended change in behavior. Bug: crashpad:196, crashpad:30 Change-Id: I7ec8d72f79533bd78189173261ade2ad99010bad Reviewed-on: https://chromium-review.googlesource.com/930321 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2018-02-22 12:12:26 -08:00
"linux/process_reader_linux_test.cc",
gn, linux: Build for Linux with GN This is sufficient for a native Linux build using GN. Android is not yet supported. mini_chromium side: https://crrev.com/c/833407 This also updates mini_chromium to 404f6dbf9928. c913ef97a236 gn, linux: Build for Linux with GN 404f6dbf9928 gn: Don’t use .rsp files; rationalize descriptions and output dirs Bug: crashpad:79 Change-Id: I4f3b72fd02884d77812e520fb95231b35815677d Reviewed-on: https://chromium-review.googlesource.com/833408 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-12-19 14:21:14 -05:00
"linux/system_snapshot_linux_test.cc",
linux: Refactor test modules This patch moves LoadModule() to it's own file from process_reader_linux_test.cc so that it may be used in other tests that interact with loaded modules. Change-Id: Ie4f7932d65710fc3e20b6e2488e497c5aab27cdd Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2569882 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Joshua Peraza <jperaza@chromium.org>
2020-12-03 13:24:06 -08:00
"linux/test_modules.cc",
"linux/test_modules.h",
Add ProcessSnapshotSanitized A ProcessSnapshotSanitized enables filtering possibly sensitive information from a snapshot. WebView has different privacy constraints than Chrome and needs to avoid collecting data in annotations or from stack memory that may contain PII. This CL enables: 1. Filtering annotations by name using a whitelist. 2. Filtering for crashes which reference a particular module. 3. Redacting non-essential information from stack memory. This CL does not provide a client interface to enable sanitization. Bug: crashpad:30 Change-Id: I8944c70fdcca6d6d4b7955d983320909bf871254 Reviewed-on: https://chromium-review.googlesource.com/1070472 Commit-Queue: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org>
2018-06-11 09:38:24 -07:00
"sanitized/process_snapshot_sanitized_test.cc",
android/linux: add a client interface to control sanitization Sanitization is controlled by a SanitizationInformation struct to be read from the client's memory. The address of this struct is either passed in a ClientInformation when the client requests a crash dump, or as a flag to the handler --sanitization_information. Bug: crashpad:30 Change-Id: I2744f8fb85b4fea7362b2b88faa4bef1da74e36b Reviewed-on: https://chromium-review.googlesource.com/1083143 Commit-Queue: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org>
2018-06-12 08:30:36 -07:00
"sanitized/sanitization_information_test.cc",
gn, linux: Build for Linux with GN This is sufficient for a native Linux build using GN. Android is not yet supported. mini_chromium side: https://crrev.com/c/833407 This also updates mini_chromium to 404f6dbf9928. c913ef97a236 gn, linux: Build for Linux with GN 404f6dbf9928 gn: Don’t use .rsp files; rationalize descriptions and output dirs Bug: crashpad:79 Change-Id: I4f3b72fd02884d77812e520fb95231b35815677d Reviewed-on: https://chromium-review.googlesource.com/833408 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-12-19 14:21:14 -05:00
]
[ios] Fix iOS device build. Change-Id: Ib0f5af9680b4b626df2da006789eb846cd38579d Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2081269 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Justin Cohen <justincohen@chromium.org>
2020-03-02 20:34:47 -05:00
} else if (!crashpad_is_ios) {
gn, linux: Build for Linux with GN This is sufficient for a native Linux build using GN. Android is not yet supported. mini_chromium side: https://crrev.com/c/833407 This also updates mini_chromium to 404f6dbf9928. c913ef97a236 gn, linux: Build for Linux with GN 404f6dbf9928 gn: Don’t use .rsp files; rationalize descriptions and output dirs Bug: crashpad:79 Change-Id: I4f3b72fd02884d77812e520fb95231b35815677d Reviewed-on: https://chromium-review.googlesource.com/833408 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-12-19 14:21:14 -05:00
sources += [ "crashpad_info_client_options_test.cc" ]
}
Use CrashpadInfoReader in ModuleSnapshotWin In preparation for deleting the custom CrashpadInfo reading routines in the PEImageReader and also deleting the PEImageAnnotationsReader, this change moves ModuleSnapshotWin to using the platform-independent CrashpadInfoReader. Bug: crashpad:270 Change-Id: Idad5de173200068243eacb2bb11b2d95b6438e90 Reviewed-on: https://chromium-review.googlesource.com/c/1388017 Commit-Queue: Vlad Tsyrklevich <vtsyrklevich@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-12-21 13:42:51 -08:00
if (crashpad_is_linux || crashpad_is_android || crashpad_is_fuchsia ||
crashpad_is_win) {
sources += [ "crashpad_types/crashpad_info_reader_test.cc" ]
}
fuchsia: Get CrashpadInfoReader working Bug: crashpad:196 Change-Id: Ia9bcc45891fd5cf40cccc655c4b904b1610e5932 Reviewed-on: https://chromium-review.googlesource.com/875117 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-01-18 14:34:41 -08:00
if (crashpad_is_linux || crashpad_is_android || crashpad_is_fuchsia) {
fuchsia: Port ElfImageReader and (some of) its tests (Still need to avoid fork()-dependence for the non-self tests.) Bug: crashpad:196 Change-Id: Ib34fe33c7ec295881c1f555995072d9ff742647f Reviewed-on: https://chromium-review.googlesource.com/876650 Reviewed-by: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2018-01-19 14:03:34 -08:00
sources += [
fuchsia: Make ImageAnnotationReader[Test] work Ports the test away from fork() to MultiprocessExec. Requires a Fuchsia SDK that includes the fix in https://fuchsia-review.googlesource.com/c/zircon/+/125081. Bug: crashpad:196, crashpad:215 Change-Id: Ia8d382cebe8d2ffc8d877e5249baf0e58aee248c Reviewed-on: https://chromium-review.googlesource.com/927355 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-02-20 16:10:20 -08:00
"crashpad_types/image_annotation_reader_test.cc",
fuchsia: Port ElfImageReader and (some of) its tests (Still need to avoid fork()-dependence for the non-self tests.) Bug: crashpad:196 Change-Id: Ib34fe33c7ec295881c1f555995072d9ff742647f Reviewed-on: https://chromium-review.googlesource.com/876650 Reviewed-by: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2018-01-19 14:03:34 -08:00
"elf/elf_image_reader_test.cc",
"elf/elf_image_reader_test_note.S",
]
fuchsia: Get CrashpadInfoReader working Bug: crashpad:196 Change-Id: Ia9bcc45891fd5cf40cccc655c4b904b1610e5932 Reviewed-on: https://chromium-review.googlesource.com/875117 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-01-18 14:34:41 -08:00
}
gn: Avoid depending on BUILDCONFIG.gn globals Goes with https://chromium-review.googlesource.com/c/chromium/mini_chromium/+/834648. Includes mini_chromium DEPS roll to pull in https://chromium.googlesource.com/chromium/mini_chromium/+/edfe51ce818e55eae73ab3f144a360e855533888 Bug: crashpad:79, crashpad:196 Change-Id: Ib45cc738aecf9ae727f8faeff81f3b71e2dc9de8 Reviewed-on: https://chromium-review.googlesource.com/834543 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2017-12-19 15:31:04 -08:00
if (crashpad_is_win) {
gn: Move sources out to explicit blocks This avoids relying on set_sources_assignment_filter, and so gets closer to a correct set of files to build on Fuchsia. Bug: crashpad:79, crashpad:196 Change-Id: Ib7daa5137935113c6645b72eb1dedd943a9db96e Reviewed-on: https://chromium-review.googlesource.com/797672 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-29 11:59:18 -08:00
sources += [
"win/cpu_context_win_test.cc",
"win/exception_snapshot_win_test.cc",
"win/extra_memory_ranges_test.cc",
Refactor PEImageAnnotationsReader test In preparation for deleting the PEImageAnnotationsReader (and replacing it with the generic ImageAnnotationsReader) change the PEImageAnnotationsReader test to be a ModuleSnapshotWin test instead. The tests are still useful for testing the annotations on the module snapshot. Bug: crashpad:270 Change-Id: Ibbbc69c72ca2eb98bfae9dc9b57bf28e9d3f12e2 Reviewed-on: https://chromium-review.googlesource.com/c/1388018 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Vlad Tsyrklevich <vtsyrklevich@chromium.org>
2018-12-20 20:44:15 -08:00
"win/module_snapshot_win_test.cc",
gn: Move sources out to explicit blocks This avoids relying on set_sources_assignment_filter, and so gets closer to a correct set of files to build on Fuchsia. Bug: crashpad:79, crashpad:196 Change-Id: Ib7daa5137935113c6645b72eb1dedd943a9db96e Reviewed-on: https://chromium-review.googlesource.com/797672 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-29 11:59:18 -08:00
"win/pe_image_reader_test.cc",
"win/process_reader_win_test.cc",
"win/process_snapshot_win_test.cc",
"win/system_snapshot_win_test.cc",
]
fuchsia: Disable TimeZone.Basic test as timezones are non-functional TZ related functionality isn't working in Fuchsia right now https://fuchsia.googlesource.com/zircon/+/master/third_party/ulib/musl/src/time/__tz.c#9 so this test has no chance of working. Disable for now. Bug: crashpad:196 Change-Id: I77c3d38e5f5fc98f2e7bf8c493df269eb142ce75 Reviewed-on: https://chromium-review.googlesource.com/923201 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-02-16 09:48:15 -08:00
} else if (!crashpad_is_fuchsia) {
# Timezones are currently non-functional on Fuchsia:
# https://fuchsia.googlesource.com/zircon/+/master/third_party/ulib/musl/src/time/__tz.c#9
# https://crashpad.chromium.org/bug/196. Relevant upstream bugs are ZX-337
# and ZX-1731.
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
sources += [ "posix/timezone_test.cc" ]
}
fuchsia: Add some thread reading to ProcessReader and a test This fills out Threads() in ProcessReader, gathering some information for which there's system calls, and adds some basic tests for ProcessReader on Fuchsia. Bug: crashpad:196 Change-Id: I0738e77121c90a8b883267c1df0fcfc6621674d7 Reviewed-on: https://chromium-review.googlesource.com/929350 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-02-22 11:06:35 -08:00
if (crashpad_is_fuchsia) {
fuchsia: Include address space information in process snapshot This plumbs some of the ZX_INFO_PROCESS_MAPS information out into MINIDUMP_MEMORY_INFO. The mapping loses some information that Zircon provides, and some of the data that Windows would provide isn't available (for example, AllocationProtect). But this gives a general idea of the memory layout of the process to check for bad pointers, etc. when inspecting crashes. Bug: fuchsia:DX-615 Change-Id: I2d7c02be0996672253cf0b1eb6a60b0a55e6033b Reviewed-on: https://chromium-review.googlesource.com/c/1377089 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-12-14 13:17:43 -08:00
sources += [
"fuchsia/process_reader_fuchsia_test.cc",
"fuchsia/process_snapshot_fuchsia_test.cc",
]
fuchsia: Add some thread reading to ProcessReader and a test This fills out Threads() in ProcessReader, gathering some information for which there's system calls, and adds some basic tests for ProcessReader on Fuchsia. Bug: crashpad:196 Change-Id: I0738e77121c90a8b883267c1df0fcfc6621674d7 Reviewed-on: https://chromium-review.googlesource.com/929350 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-02-22 11:06:35 -08:00
}
gn, linux: Build for Linux with GN This is sufficient for a native Linux build using GN. Android is not yet supported. mini_chromium side: https://crrev.com/c/833407 This also updates mini_chromium to 404f6dbf9928. c913ef97a236 gn, linux: Build for Linux with GN 404f6dbf9928 gn: Don’t use .rsp files; rationalize descriptions and output dirs Bug: crashpad:79 Change-Id: I4f3b72fd02884d77812e520fb95231b35815677d Reviewed-on: https://chromium-review.googlesource.com/833408 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-12-19 14:21:14 -05:00
# public_configs isn’t quite right. snapshot_test_link sets ldflags, and
# what’s really needed is a way to push ldflags to dependent targets that
# produce linker output. Luckily in this case, all dependents do produce
# linker output. https://crbug.com/796183.
public_configs = [ ":snapshot_test_link" ]
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
deps = [
":test_support",
ios: Update XCUITests to check various crash type exception codes. Bug: crashpad:31 Change-Id: I804def3be0050b3e6f15d7d77d0b70184c380673 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3087722 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2021-10-28 17:02:27 -04:00
"$mini_chromium_source_parent:base",
ios: Extract common targets to be shared for iOS. Move some common files out of client and handler for iOS usage. Bug: crashpad: 31 Change-Id: I1933eaaa7580a81017c52b77dfb636a8fa31ee78 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2851059 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Justin Cohen <justincohen@chromium.org>
2021-04-27 21:27:09 -04:00
"../client:common",
Rework GN files to start to support building standalone, and also in Chromium - Adds a .gn and a build/BUILDCONFIG.gn that uses mini_chromium's build/BUILD.gn. - Adds some stub BUILD.gn files in locations where Chromium expects them (in //build, //testing, //third_party) containing empty targets/configs. These are no-ops in standalone builds, but add functionality when building in Chromium. This is in preference to having a global bool that conditionally does Chromium-y things in the Crashpad build files. These stub files are all contained in a secondary source root in build/chromium_compatibility, referred to by //.gn. - Adds //base/BUILD.gn which forwards to mini_chromium/base. This is only used when building standalone so that both Chromium and Crashpad can refer to it as "//base". - Changes references to other Crashpad targets to be relatively specified so that they work when the root of the project is //, and also when it's //third_party/crashpad/crashpad as it is in Chromium. - Moves any error-causing Mac/Win-specific files into explicit if (is_mac) or if (is_win) blocks as part of removing the dependency on set_sources_assignment_filter(). As yet unresolved: - CRASHPAD_IN_CHROMIUM needs to be removed when standalone; to be tackled in a follow up. - Not sure what to do with zlib yet, the build file currently assumes "in Chromium" too, and similarly having Crashpad //third_party/zlib:zlib pointing at itself doesn't work. Bug: crashpad:79 Change-Id: I6a7dda214e4b3b14a60c1ed285267ab97432a1a8 Reviewed-on: https://chromium-review.googlesource.com/777410 Reviewed-by: Mark Mentovai <mark@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-28 10:31:13 -08:00
"../compat",
Make “gn check” pass Change-Id: Ia7a215e1a2d0a3b1868b00c5d47b46ef8a675cdc Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2144917 Reviewed-by: Justin Cohen <justincohen@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org> Commit-Queue: Mark Mentovai <mark@chromium.org>
2020-04-10 17:40:41 -04:00
"../minidump:format",
Rework GN files to start to support building standalone, and also in Chromium - Adds a .gn and a build/BUILDCONFIG.gn that uses mini_chromium's build/BUILD.gn. - Adds some stub BUILD.gn files in locations where Chromium expects them (in //build, //testing, //third_party) containing empty targets/configs. These are no-ops in standalone builds, but add functionality when building in Chromium. This is in preference to having a global bool that conditionally does Chromium-y things in the Crashpad build files. These stub files are all contained in a secondary source root in build/chromium_compatibility, referred to by //.gn. - Adds //base/BUILD.gn which forwards to mini_chromium/base. This is only used when building standalone so that both Chromium and Crashpad can refer to it as "//base". - Changes references to other Crashpad targets to be relatively specified so that they work when the root of the project is //, and also when it's //third_party/crashpad/crashpad as it is in Chromium. - Moves any error-causing Mac/Win-specific files into explicit if (is_mac) or if (is_win) blocks as part of removing the dependency on set_sources_assignment_filter(). As yet unresolved: - CRASHPAD_IN_CHROMIUM needs to be removed when standalone; to be tackled in a follow up. - Not sure what to do with zlib yet, the build file currently assumes "in Chromium" too, and similarly having Crashpad //third_party/zlib:zlib pointing at itself doesn't work. Bug: crashpad:79 Change-Id: I6a7dda214e4b3b14a60c1ed285267ab97432a1a8 Reviewed-on: https://chromium-review.googlesource.com/777410 Reviewed-by: Mark Mentovai <mark@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-28 10:31:13 -08:00
"../test",
mac/arm64: recognize “Apple M1” as a valid CPU vendor The DTK reported “Apple processor” in this spot, but shipping hardware now seems to use “Apple M1”. The DTK is no longer relevant, but for some degree of future-proofing, look for “Apple ” as prefix in the test. Test: snapshot_test SystemSnapshotMacTest.CPUVendor Bug: chromium:1222625 Change-Id: I6ead87ebe9aa078ef9a95e5bcc6a9e5ca8c3b55a Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2976787 Reviewed-by: Nico Weber <thakis@chromium.org> Commit-Queue: Mark Mentovai <mark@chromium.org>
2021-06-22 10:55:22 -04:00
"../third_party/googletest:googlemock",
Update gtest to e3f0319d89f4cbf32993de595d984183b1a9fc57 I’m most interested in picking up 1b3eb6ef3462, “Explicitly define copy constructors used in googletest tests.” This also reorganizes files and rewrites text to refer to this project as Google Test and googletest (and Google Mock and googlemock), as it prefers to be known. Some filenames are left at gtest_* following the precedent set by gtest itself. For example, #include "gtest/gtest.h" is still used, so #include "test/gtest_death.h" is retained too. gtest_all_test OutputFileHelpersTest.GetCurrentExecutableName hard-codes the expected executable name as gtest_all_test among other options that do not include googletest_all_test, so test executables retain their names as well. fb19f57880f6 Add GTEST_BRIEF option 3549237957a1 Ensure that gtest/gmock pkgconfig requirements specify version 189299e957bb Merge branch 'master' into quiet-flag 5504ded3ab5c Fix a typo in .travis.yml 6ed4e7168f54 Replace the last instance of `throw()` with `noexcept`. NFC 879fd9b45299 Remove duplicate codes existed in get-nprocessors.sh 644f3a992c28 gtest-unittest-api_test - fix warning in clang build 0b6d567619fe Remove redundant .c_str() be3ac45cf673 fix signed/unsigned comparison issue (on OpenBSD) b51a49e0cb82 Merge pull request #2773 from Quuxplusone:replace-noexcept c2032090f373 Merge pull request #2772 from Quuxplusone:travis 4fe5ac53337e Merge pull request #2756 from Conan-Kudo:fix-pkgconfig-reqs 373d72b6986f Googletest export 4c8e6a9fe1c8 Merge pull request #2810 from ptahmose:master 71d5df6c6b67 Merge pull request #2802 from e-i-n-s:fix_clang_warning dcc92d0ab6c4 Merge pull request #2805 from pepsiman:patch-1 4f002f1e236c VariadicMatcher needs a non-defaulted move constructor for compile-time performance 9d580ea80592 Enable protobuf printing for open-source proto messages 766ac2e1a413 Remove all uses of GTEST_DISALLOW_{MOVE_,}ASSIGN_ 11b3cec177b1 Fix a -Wdeprecated warning 01c0ff5e2373 Fix a -Wdeprecated warning c7d8ec72cc4b Fix a -Wdeprecated warning 1b066f4edfd5 Add -Wdeprecated to the build configuration 4bab55dc54b4 Removed a typo in README.md a67701056425 Googletest export fb5d9b66c5b0 Googletest export 1b3eb6ef3462 Googletest export b0e53e2d64db Merge pull request #2797 from Jyun-Neng:master d7ca9af0049e Googletest export 955552518b4e Googletest export ef25d27d4604 Merge pull request #2815 from Quuxplusone:simple 129329787429 Googletest export b99b421d8d68 Merge pull request #2818 from inazarenko:master 472cd8fd8b1c Merge pull request #2818 from inazarenko:master 3cfb4117f7e5 Googletest export 0eea2e9fc634 Googletest export a9f6c1ed1401 Googletest export 1a9c3e441407 Merge pull request #2830 from keshavgbpecdelhi:patch-1 e589a3371705 Merge pull request #2751 from calumr:quiet-flag Change-Id: Id788a27aa884ef68a21bae6c178cd456f5f6f2b0 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2186009 Reviewed-by: Joshua Peraza <jperaza@chromium.org> Commit-Queue: Mark Mentovai <mark@chromium.org>
2020-05-06 20:39:19 -04:00
"../third_party/googletest:googletest",
Rework GN files to start to support building standalone, and also in Chromium - Adds a .gn and a build/BUILDCONFIG.gn that uses mini_chromium's build/BUILD.gn. - Adds some stub BUILD.gn files in locations where Chromium expects them (in //build, //testing, //third_party) containing empty targets/configs. These are no-ops in standalone builds, but add functionality when building in Chromium. This is in preference to having a global bool that conditionally does Chromium-y things in the Crashpad build files. These stub files are all contained in a secondary source root in build/chromium_compatibility, referred to by //.gn. - Adds //base/BUILD.gn which forwards to mini_chromium/base. This is only used when building standalone so that both Chromium and Crashpad can refer to it as "//base". - Changes references to other Crashpad targets to be relatively specified so that they work when the root of the project is //, and also when it's //third_party/crashpad/crashpad as it is in Chromium. - Moves any error-causing Mac/Win-specific files into explicit if (is_mac) or if (is_win) blocks as part of removing the dependency on set_sources_assignment_filter(). As yet unresolved: - CRASHPAD_IN_CHROMIUM needs to be removed when standalone; to be tackled in a follow up. - Not sure what to do with zlib yet, the build file currently assumes "in Chromium" too, and similarly having Crashpad //third_party/zlib:zlib pointing at itself doesn't work. Bug: crashpad:79 Change-Id: I6a7dda214e4b3b14a60c1ed285267ab97432a1a8 Reviewed-on: https://chromium-review.googlesource.com/777410 Reviewed-by: Mark Mentovai <mark@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-28 10:31:13 -08:00
"../util",
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
]
ios: Migrate ios/snapshot to reading intermediate dumps. Change-Id: Ib7715e642fa685a5f607239d07dcb68868cacb09 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2883523 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2021-05-26 15:12:33 -04:00
if (crashpad_is_ios) {
ios: Fix typo in checking thread_times values. Change-Id: I4199b5b149d7792dcfb8a3b8de571026b1e98521 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3264806 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Justin Cohen <justincohen@chromium.org>
2021-11-05 15:23:47 -04:00
deps += [
":snapshot_test_ios_data",
"../minidump",
]
ios: Migrate ios/snapshot to reading intermediate dumps. Change-Id: Ib7715e642fa685a5f607239d07dcb68868cacb09 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2883523 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2021-05-26 15:12:33 -04:00
}
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
data_deps = [
":crashpad_snapshot_test_module",
":crashpad_snapshot_test_module_large",
":crashpad_snapshot_test_module_small",
]
gn: Avoid depending on BUILDCONFIG.gn globals Goes with https://chromium-review.googlesource.com/c/chromium/mini_chromium/+/834648. Includes mini_chromium DEPS roll to pull in https://chromium.googlesource.com/chromium/mini_chromium/+/edfe51ce818e55eae73ab3f144a360e855533888 Bug: crashpad:79, crashpad:196 Change-Id: Ib45cc738aecf9ae727f8faeff81f3b71e2dc9de8 Reviewed-on: https://chromium-review.googlesource.com/834543 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2017-12-19 15:31:04 -08:00
if (crashpad_is_mac) {
apple: Convert GN libs lists to frameworks. GN recently added support for Apple frameworks to link, rather than overloading the libs lists. This pulls .frameworks out of the libs lists, so that GN can stop supporting .frameworks in libs in the future. Roll mini_chromium ae14a14ab..cd26c5101 $ git log ae14a14ab..cd26c5101 --date=short --no-merges --format='%ad %ae %s' 2020-07-01 rsesek@chromium.org apple: Expand {{framework_dirs}} and {{frameworks}} in the toolchain. Bug: chromium:1052560 Change-Id: Id70bceb57174a52c6f4a7f72378a3ee0ae89f64d Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2278022 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Robert Sesek <rsesek@chromium.org>
2020-07-01 14:34:38 -04:00
frameworks = [ "OpenCL.framework" ]
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
data_deps += [
":crashpad_snapshot_test_module_crashy_initializer",
":crashpad_snapshot_test_no_op",
]
}
gn, android: Build for Android with GN With a companion mini_chromium change at https://crrev.com/c/841203, it’s possible to configure via “gn args” as follows: android_ndk = "/android/android-ndk-r16" target_cpu = "x86_64" target_os = "android" Note that a standalone toolchain is not required. Bug: crashpad:30, crashpad:79 Change-Id: Ica55bdcb82c730909c05dd9fecb40a74eca78c8a Reviewed-on: https://chromium-review.googlesource.com/841286 Reviewed-by: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org>
2017-12-21 17:54:12 -05:00
if (crashpad_is_linux || crashpad_is_android) {
gn, linux: Build for Linux with GN This is sufficient for a native Linux build using GN. Android is not yet supported. mini_chromium side: https://crrev.com/c/833407 This also updates mini_chromium to 404f6dbf9928. c913ef97a236 gn, linux: Build for Linux with GN 404f6dbf9928 gn: Don’t use .rsp files; rationalize descriptions and output dirs Bug: crashpad:79 Change-Id: I4f3b72fd02884d77812e520fb95231b35815677d Reviewed-on: https://chromium-review.googlesource.com/833408 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-12-19 14:21:14 -05:00
libs = [ "dl" ]
}
Added MIPS support to crashpad. Modified gyp/gn files to support MIPS targets. Implemented thread_info, cpu_context, signal context classes for MIPS target. Addressed MIPS specific signal ordering. Added "MIPS Technologies, Inc." to AUTHORS file. Bug: crashpad:232 Change-Id: Ibfc221ba54088e95f984b9dc6be5fd52f86abcc2 Reviewed-on: https://chromium-review.googlesource.com/1064594 Commit-Queue: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2018-07-10 11:17:22 +02:00
if ((crashpad_is_linux || crashpad_is_android || crashpad_is_fuchsia) &&
target_cpu != "mipsel" && target_cpu != "mips64el") {
gn: Guard addition of ELF test target Fix Windows- and Mac-in-Chromium GN builds. Bug: crashpad:79 Change-Id: I952f364ed679a13f656a8db18fb4d1fbf5858c17 Reviewed-on: https://chromium-review.googlesource.com/900206 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-02-02 14:04:48 -08:00
data_deps += [ ":crashpad_snapshot_test_both_dt_hash_styles" ]
}
gn: Avoid depending on BUILDCONFIG.gn globals Goes with https://chromium-review.googlesource.com/c/chromium/mini_chromium/+/834648. Includes mini_chromium DEPS roll to pull in https://chromium.googlesource.com/chromium/mini_chromium/+/edfe51ce818e55eae73ab3f144a360e855533888 Bug: crashpad:79, crashpad:196 Change-Id: Ib45cc738aecf9ae727f8faeff81f3b71e2dc9de8 Reviewed-on: https://chromium-review.googlesource.com/834543 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2017-12-19 15:31:04 -08:00
if (crashpad_is_win) {
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
cflags = [ "/wd4201" ] # nonstandard extension used : nameless struct/union
data_deps += [
":crashpad_snapshot_test_annotations",
":crashpad_snapshot_test_crashing_child",
":crashpad_snapshot_test_dump_without_crashing",
":crashpad_snapshot_test_extra_memory_ranges",
":crashpad_snapshot_test_image_reader",
":crashpad_snapshot_test_image_reader_module",
]
}
}
ios: Fix typo in checking thread_times values. Change-Id: I4199b5b149d7792dcfb8a3b8de571026b1e98521 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3264806 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Justin Cohen <justincohen@chromium.org>
2021-11-05 15:23:47 -04:00
bundle_data("snapshot_test_ios_data") {
testonly = true
ios: Handle empty stack in GenerateStackMemoryFromFrames. This fixes a _LIBCPP_ASSERT vector[] index out of bounds error, caught by fuzzer. Bug: 1274178 Change-Id: I95f3fbe450209a24ccc0229741ea752990e18ed6 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3307697 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2021-11-29 15:01:00 -05:00
sources = [
"ios/testdata/crash-1fa088dda0adb41459d063078a0f384a0bb8eefa",
"ios/testdata/crash-5726011582644224",
ios: Limit depth of intermediate dump parser. Limit the parser stack to 10 to prevent malformed intermediate dumps from causing a stack overflow. Bug: 1321382 Change-Id: I880e80de585b0fb18f0c383102b9227d6ffbfa76 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3637719 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2022-05-10 12:34:01 -04:00
"ios/testdata/crash-6605504629637120",
ios: Handle empty stack in GenerateStackMemoryFromFrames. This fixes a _LIBCPP_ASSERT vector[] index out of bounds error, caught by fuzzer. Bug: 1274178 Change-Id: I95f3fbe450209a24ccc0229741ea752990e18ed6 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3307697 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2021-11-29 15:01:00 -05:00
]
ios: Fix typo in checking thread_times values. Change-Id: I4199b5b149d7792dcfb8a3b8de571026b1e98521 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3264806 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Justin Cohen <justincohen@chromium.org>
2021-11-05 15:23:47 -04:00
outputs = [ "{{bundle_resources_dir}}/crashpad_test_data/" +
"{{source_root_relative_dir}}/{{source_file_part}}" ]
}
gn: add templates for executables and loadable_modules When building in chromium, executables and loadable_modules should depend on: //build/config:exe_and_shlib_deps which, among other things, may be needed to introduce a dependency on a custom libc++. Bug: crashpad:30 Change-Id: Ic46a3cf5b46bdac09cca22950f9236e0776ba44a Reviewed-on: https://chromium-review.googlesource.com/974713 Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-03-21 19:18:07 -07:00
crashpad_loadable_module("crashpad_snapshot_test_module") {
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
testonly = true
Reformat all gn files Port of chromium-side https://chromium-review.googlesource.com/c/chromium/src/+/1997899 Bug: chromium:1041419 Change-Id: Ic7afefa0dea024da37fe4bb0f965840a160e2166 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2015428 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2020-01-23 08:00:33 -05:00
sources = [ "crashpad_info_client_options_test_module.cc" ]
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
deps = [
[third_party] Make mini_chromium relocatable This will accommodate moving third_party/mini_chromium around. The default location is unchanged for now. There are GN variables that may need to be updated when Fuchsia's source re-organizes its layout: * mini_chromium_source_parent : this contains a BUILD.gn with groups and encloses the mini_chromium_source_root. This is controlled by the structure of the project that depends on this project. * _mini_chromium_source_root : this is what is normally checked out from git, the upstream source directory * mini_chromium_import_root : points inside source_root to make GN files accessible. This first step breaks out case logic for "if (crashpad_is_in_fuchsia)" even if the value is unchanged for now. This will faciliate a smaller change when Fuchsia re-structures third_party sources. Change-Id: I09e5362f4be8fdb440e3891422881b1053052341 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3062424 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Mark Mentovai <mark@chromium.org>
2021-07-28 23:57:54 +00:00
"$mini_chromium_source_parent:base",
ios: Update XCUITests to check various crash type exception codes. Bug: crashpad:31 Change-Id: I804def3be0050b3e6f15d7d77d0b70184c380673 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3087722 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2021-10-28 17:02:27 -04:00
"../client",
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
]
[fuchsia] Temporarily disable hwasan from crashpad tests Much of crashpad's unittests propagate tagged pointers to fuchsia syscalls which do not accept tagged values. Rather than fixing them all right now, just ensure that the tests do not build with the hwasan variant if enabled. Bug: fxbug.dev/108368 Change-Id: Ib32eb95ba671a6b55694075b68c7fbbb733cf501 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/4175438 Reviewed-by: Francois Rousseau <frousseau@google.com> Commit-Queue: Francois Rousseau <frousseau@google.com>
2023-01-17 23:18:15 +00:00
if (crashpad_is_in_fuchsia) {
# TODO(fxbug.dev/108368): Remove this once the underlying issue is addressed.
exclude_toolchain_tags = [ "hwasan" ]
}
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
}
gn: add templates for executables and loadable_modules When building in chromium, executables and loadable_modules should depend on: //build/config:exe_and_shlib_deps which, among other things, may be needed to introduce a dependency on a custom libc++. Bug: crashpad:30 Change-Id: Ic46a3cf5b46bdac09cca22950f9236e0776ba44a Reviewed-on: https://chromium-review.googlesource.com/974713 Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-03-21 19:18:07 -07:00
crashpad_loadable_module("crashpad_snapshot_test_module_large") {
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
testonly = true
Reformat all gn files Port of chromium-side https://chromium-review.googlesource.com/c/chromium/src/+/1997899 Bug: chromium:1041419 Change-Id: Ic7afefa0dea024da37fe4bb0f965840a160e2166 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2015428 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2020-01-23 08:00:33 -05:00
sources = [ "crashpad_info_size_test_module.cc" ]
Fix CrashpadInfoSizes_ClientOptions/CrashpadInfoSizes_ClientOptions These tests needed to be updated to expose CrashpadInfo in the same way as the main CrashpadInfo g_crashpad_info is found on Linux/Android/Fuchsia. Unfortunately, while the tests pass on Fuchsia when run in isolation, the implementation of dlclose() on Fuchsia currently does nothing. So, if the full test suite is run, there's interference between the test modules (i.e. the values in _small vs. the values in _large), so the tests fail. I filed ZX-1728 upstream about this to see if it might be implemented, or if the test will need to spawn a clean child to do the module load tests in. Bug: crashpad:196 Change-Id: I9ee01b142a29c508c6967dc83da824afa254d379 Reviewed-on: https://chromium-review.googlesource.com/923182 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2018-02-16 09:55:34 -08:00
deps = []
if (crashpad_is_linux || crashpad_is_android || crashpad_is_fuchsia) {
sources += [ "crashpad_info_size_test_note.S" ]
deps += [ "../util" ]
}
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
defines = [ "CRASHPAD_INFO_SIZE_TEST_MODULE_LARGE" ]
[third_party] Make mini_chromium relocatable This will accommodate moving third_party/mini_chromium around. The default location is unchanged for now. There are GN variables that may need to be updated when Fuchsia's source re-organizes its layout: * mini_chromium_source_parent : this contains a BUILD.gn with groups and encloses the mini_chromium_source_root. This is controlled by the structure of the project that depends on this project. * _mini_chromium_source_root : this is what is normally checked out from git, the upstream source directory * mini_chromium_import_root : points inside source_root to make GN files accessible. This first step breaks out case logic for "if (crashpad_is_in_fuchsia)" even if the value is unchanged for now. This will faciliate a smaller change when Fuchsia re-structures third_party sources. Change-Id: I09e5362f4be8fdb440e3891422881b1053052341 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3062424 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Mark Mentovai <mark@chromium.org>
2021-07-28 23:57:54 +00:00
deps += [ "$mini_chromium_source_parent:base" ]
[fuchsia] Temporarily disable hwasan from crashpad tests Much of crashpad's unittests propagate tagged pointers to fuchsia syscalls which do not accept tagged values. Rather than fixing them all right now, just ensure that the tests do not build with the hwasan variant if enabled. Bug: fxbug.dev/108368 Change-Id: Ib32eb95ba671a6b55694075b68c7fbbb733cf501 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/4175438 Reviewed-by: Francois Rousseau <frousseau@google.com> Commit-Queue: Francois Rousseau <frousseau@google.com>
2023-01-17 23:18:15 +00:00
if (crashpad_is_in_fuchsia) {
# TODO(fxbug.dev/108368): Remove this once the underlying issue is addressed.
exclude_toolchain_tags = [ "hwasan" ]
}
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
}
gn: add templates for executables and loadable_modules When building in chromium, executables and loadable_modules should depend on: //build/config:exe_and_shlib_deps which, among other things, may be needed to introduce a dependency on a custom libc++. Bug: crashpad:30 Change-Id: Ic46a3cf5b46bdac09cca22950f9236e0776ba44a Reviewed-on: https://chromium-review.googlesource.com/974713 Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-03-21 19:18:07 -07:00
crashpad_loadable_module("crashpad_snapshot_test_module_small") {
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
testonly = true
Reformat all gn files Port of chromium-side https://chromium-review.googlesource.com/c/chromium/src/+/1997899 Bug: chromium:1041419 Change-Id: Ic7afefa0dea024da37fe4bb0f965840a160e2166 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2015428 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2020-01-23 08:00:33 -05:00
sources = [ "crashpad_info_size_test_module.cc" ]
Fix CrashpadInfoSizes_ClientOptions/CrashpadInfoSizes_ClientOptions These tests needed to be updated to expose CrashpadInfo in the same way as the main CrashpadInfo g_crashpad_info is found on Linux/Android/Fuchsia. Unfortunately, while the tests pass on Fuchsia when run in isolation, the implementation of dlclose() on Fuchsia currently does nothing. So, if the full test suite is run, there's interference between the test modules (i.e. the values in _small vs. the values in _large), so the tests fail. I filed ZX-1728 upstream about this to see if it might be implemented, or if the test will need to spawn a clean child to do the module load tests in. Bug: crashpad:196 Change-Id: I9ee01b142a29c508c6967dc83da824afa254d379 Reviewed-on: https://chromium-review.googlesource.com/923182 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2018-02-16 09:55:34 -08:00
deps = []
if (crashpad_is_linux || crashpad_is_android || crashpad_is_fuchsia) {
sources += [ "crashpad_info_size_test_note.S" ]
deps += [ "../util" ]
}
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
defines = [ "CRASHPAD_INFO_SIZE_TEST_MODULE_SMALL" ]
[third_party] Make mini_chromium relocatable This will accommodate moving third_party/mini_chromium around. The default location is unchanged for now. There are GN variables that may need to be updated when Fuchsia's source re-organizes its layout: * mini_chromium_source_parent : this contains a BUILD.gn with groups and encloses the mini_chromium_source_root. This is controlled by the structure of the project that depends on this project. * _mini_chromium_source_root : this is what is normally checked out from git, the upstream source directory * mini_chromium_import_root : points inside source_root to make GN files accessible. This first step breaks out case logic for "if (crashpad_is_in_fuchsia)" even if the value is unchanged for now. This will faciliate a smaller change when Fuchsia re-structures third_party sources. Change-Id: I09e5362f4be8fdb440e3891422881b1053052341 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3062424 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Mark Mentovai <mark@chromium.org>
2021-07-28 23:57:54 +00:00
deps += [ "$mini_chromium_source_parent:base" ]
[fuchsia] Temporarily disable hwasan from crashpad tests Much of crashpad's unittests propagate tagged pointers to fuchsia syscalls which do not accept tagged values. Rather than fixing them all right now, just ensure that the tests do not build with the hwasan variant if enabled. Bug: fxbug.dev/108368 Change-Id: Ib32eb95ba671a6b55694075b68c7fbbb733cf501 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/4175438 Reviewed-by: Francois Rousseau <frousseau@google.com> Commit-Queue: Francois Rousseau <frousseau@google.com>
2023-01-17 23:18:15 +00:00
if (crashpad_is_in_fuchsia) {
# TODO(fxbug.dev/108368): Remove this once the underlying issue is addressed.
exclude_toolchain_tags = [ "hwasan" ]
}
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
}
Added MIPS support to crashpad. Modified gyp/gn files to support MIPS targets. Implemented thread_info, cpu_context, signal context classes for MIPS target. Addressed MIPS specific signal ordering. Added "MIPS Technologies, Inc." to AUTHORS file. Bug: crashpad:232 Change-Id: Ibfc221ba54088e95f984b9dc6be5fd52f86abcc2 Reviewed-on: https://chromium-review.googlesource.com/1064594 Commit-Queue: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2018-07-10 11:17:22 +02:00
if ((crashpad_is_linux || crashpad_is_android || crashpad_is_fuchsia) &&
target_cpu != "mipsel" && target_cpu != "mips64el") {
gn: add templates for executables and loadable_modules When building in chromium, executables and loadable_modules should depend on: //build/config:exe_and_shlib_deps which, among other things, may be needed to introduce a dependency on a custom libc++. Bug: crashpad:30 Change-Id: Ic46a3cf5b46bdac09cca22950f9236e0776ba44a Reviewed-on: https://chromium-review.googlesource.com/974713 Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-03-21 19:18:07 -07:00
crashpad_loadable_module("crashpad_snapshot_test_both_dt_hash_styles") {
Read either DT_HASH or DT_GNU_HASH to determine the size of DT_SYMTAB Without the section headers for the symbol table, there's no direct way to calculate the number of entries in the table. DT_HASH and DT_GNU_HASH are auxiliary tables that are designed to make symbol lookup faster. DT_HASH is the original and is theoretically mandatory. DT_GNU_HASH is the new-and-improved, but is more complex. In practice, however, an Android build (at least vs. API 16) has only DT_HASH, and not DT_GNU_HASH, and a Fuchsia build has only DT_GNU_HASH but not DT_HASH. So, both are tried. This change does not actually use the data in these tables to improve the speed of symbol lookup, but instead only uses them to correctly terminate the linear search. DT_HASH contains the total number of symbols in the symbol table fairly directly because there is an entry for each symbol table entry in the hash table, so the number is the same. DT_GNU_HASH regrettably does not. Instead, it's necessary to walk the buckets and chain structure to find the largest entry. DT_GNU_HASH doesn't appear in any "real" documentation that I'm aware of, other than the binutils code (at least as far as I know). Some more-and-less-useful references: - https://flapenguin.me/2017/04/24/elf-lookup-dt-hash/ - https://flapenguin.me/2017/05/10/elf-lookup-dt-gnu-hash/ - http://deroko.phearless.org/dt_gnu_hash.txt - https://sourceware.org/ml/binutils/2006-10/msg00377.html Change-Id: I7cfc4372f29efc37446f0931d22a1f790e44076f Bug: crashpad:213, crashpad:196 Reviewed-on: https://chromium-review.googlesource.com/876879 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2018-01-30 14:30:50 -08:00
testonly = true
Reformat all gn files Port of chromium-side https://chromium-review.googlesource.com/c/chromium/src/+/1997899 Bug: chromium:1041419 Change-Id: Ic7afefa0dea024da37fe4bb0f965840a160e2166 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2015428 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2020-01-23 08:00:33 -05:00
sources = [ "hash_types_test.cc" ]
Read either DT_HASH or DT_GNU_HASH to determine the size of DT_SYMTAB Without the section headers for the symbol table, there's no direct way to calculate the number of entries in the table. DT_HASH and DT_GNU_HASH are auxiliary tables that are designed to make symbol lookup faster. DT_HASH is the original and is theoretically mandatory. DT_GNU_HASH is the new-and-improved, but is more complex. In practice, however, an Android build (at least vs. API 16) has only DT_HASH, and not DT_GNU_HASH, and a Fuchsia build has only DT_GNU_HASH but not DT_HASH. So, both are tried. This change does not actually use the data in these tables to improve the speed of symbol lookup, but instead only uses them to correctly terminate the linear search. DT_HASH contains the total number of symbols in the symbol table fairly directly because there is an entry for each symbol table entry in the hash table, so the number is the same. DT_GNU_HASH regrettably does not. Instead, it's necessary to walk the buckets and chain structure to find the largest entry. DT_GNU_HASH doesn't appear in any "real" documentation that I'm aware of, other than the binutils code (at least as far as I know). Some more-and-less-useful references: - https://flapenguin.me/2017/04/24/elf-lookup-dt-hash/ - https://flapenguin.me/2017/05/10/elf-lookup-dt-gnu-hash/ - http://deroko.phearless.org/dt_gnu_hash.txt - https://sourceware.org/ml/binutils/2006-10/msg00377.html Change-Id: I7cfc4372f29efc37446f0931d22a1f790e44076f Bug: crashpad:213, crashpad:196 Reviewed-on: https://chromium-review.googlesource.com/876879 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2018-01-30 14:30:50 -08:00
# This makes `ld` emit both .hash and .gnu.hash sections.
ldflags = [ "-Wl,--hash-style=both" ]
[fuchsia] Temporarily disable hwasan from crashpad tests Much of crashpad's unittests propagate tagged pointers to fuchsia syscalls which do not accept tagged values. Rather than fixing them all right now, just ensure that the tests do not build with the hwasan variant if enabled. Bug: fxbug.dev/108368 Change-Id: Ib32eb95ba671a6b55694075b68c7fbbb733cf501 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/4175438 Reviewed-by: Francois Rousseau <frousseau@google.com> Commit-Queue: Francois Rousseau <frousseau@google.com>
2023-01-17 23:18:15 +00:00
if (crashpad_is_in_fuchsia) {
# TODO(fxbug.dev/108368): Remove this once the underlying issue is addressed.
exclude_toolchain_tags = [ "hwasan" ]
}
Read either DT_HASH or DT_GNU_HASH to determine the size of DT_SYMTAB Without the section headers for the symbol table, there's no direct way to calculate the number of entries in the table. DT_HASH and DT_GNU_HASH are auxiliary tables that are designed to make symbol lookup faster. DT_HASH is the original and is theoretically mandatory. DT_GNU_HASH is the new-and-improved, but is more complex. In practice, however, an Android build (at least vs. API 16) has only DT_HASH, and not DT_GNU_HASH, and a Fuchsia build has only DT_GNU_HASH but not DT_HASH. So, both are tried. This change does not actually use the data in these tables to improve the speed of symbol lookup, but instead only uses them to correctly terminate the linear search. DT_HASH contains the total number of symbols in the symbol table fairly directly because there is an entry for each symbol table entry in the hash table, so the number is the same. DT_GNU_HASH regrettably does not. Instead, it's necessary to walk the buckets and chain structure to find the largest entry. DT_GNU_HASH doesn't appear in any "real" documentation that I'm aware of, other than the binutils code (at least as far as I know). Some more-and-less-useful references: - https://flapenguin.me/2017/04/24/elf-lookup-dt-hash/ - https://flapenguin.me/2017/05/10/elf-lookup-dt-gnu-hash/ - http://deroko.phearless.org/dt_gnu_hash.txt - https://sourceware.org/ml/binutils/2006-10/msg00377.html Change-Id: I7cfc4372f29efc37446f0931d22a1f790e44076f Bug: crashpad:213, crashpad:196 Reviewed-on: https://chromium-review.googlesource.com/876879 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2018-01-30 14:30:50 -08:00
}
}
ios: Update XCUITests to check various crash type exception codes. Bug: crashpad:31 Change-Id: I804def3be0050b3e6f15d7d77d0b70184c380673 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3087722 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2021-10-28 17:02:27 -04:00
if (crashpad_is_mac || crashpad_is_ios) {
gn: add templates for executables and loadable_modules When building in chromium, executables and loadable_modules should depend on: //build/config:exe_and_shlib_deps which, among other things, may be needed to introduce a dependency on a custom libc++. Bug: crashpad:30 Change-Id: Ic46a3cf5b46bdac09cca22950f9236e0776ba44a Reviewed-on: https://chromium-review.googlesource.com/974713 Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-03-21 19:18:07 -07:00
crashpad_loadable_module("crashpad_snapshot_test_module_crashy_initializer") {
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
testonly = true
sources = [
"mac/mach_o_image_annotations_reader_test_module_crashy_initializer.cc",
]
}
gn: add templates for executables and loadable_modules When building in chromium, executables and loadable_modules should depend on: //build/config:exe_and_shlib_deps which, among other things, may be needed to introduce a dependency on a custom libc++. Bug: crashpad:30 Change-Id: Ic46a3cf5b46bdac09cca22950f9236e0776ba44a Reviewed-on: https://chromium-review.googlesource.com/974713 Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-03-21 19:18:07 -07:00
crashpad_executable("crashpad_snapshot_test_no_op") {
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
testonly = true
Reformat all gn files Port of chromium-side https://chromium-review.googlesource.com/c/chromium/src/+/1997899 Bug: chromium:1041419 Change-Id: Ic7afefa0dea024da37fe4bb0f965840a160e2166 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2015428 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2020-01-23 08:00:33 -05:00
sources = [ "mac/mach_o_image_annotations_reader_test_no_op.cc" ]
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
}
}
gn: Avoid depending on BUILDCONFIG.gn globals Goes with https://chromium-review.googlesource.com/c/chromium/mini_chromium/+/834648. Includes mini_chromium DEPS roll to pull in https://chromium.googlesource.com/chromium/mini_chromium/+/edfe51ce818e55eae73ab3f144a360e855533888 Bug: crashpad:79, crashpad:196 Change-Id: Ib45cc738aecf9ae727f8faeff81f3b71e2dc9de8 Reviewed-on: https://chromium-review.googlesource.com/834543 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2017-12-19 15:31:04 -08:00
if (crashpad_is_win) {
gn: add templates for executables and loadable_modules When building in chromium, executables and loadable_modules should depend on: //build/config:exe_and_shlib_deps which, among other things, may be needed to introduce a dependency on a custom libc++. Bug: crashpad:30 Change-Id: Ic46a3cf5b46bdac09cca22950f9236e0776ba44a Reviewed-on: https://chromium-review.googlesource.com/974713 Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-03-21 19:18:07 -07:00
crashpad_executable("crashpad_snapshot_test_annotations") {
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
testonly = true
Reformat all gn files Port of chromium-side https://chromium-review.googlesource.com/c/chromium/src/+/1997899 Bug: chromium:1041419 Change-Id: Ic7afefa0dea024da37fe4bb0f965840a160e2166 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2015428 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2020-01-23 08:00:33 -05:00
sources = [ "win/crashpad_snapshot_test_annotations.cc" ]
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
deps = [
ios: Update XCUITests to check various crash type exception codes. Bug: crashpad:31 Change-Id: I804def3be0050b3e6f15d7d77d0b70184c380673 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3087722 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2021-10-28 17:02:27 -04:00
"$mini_chromium_source_parent:base",
Rework GN files to start to support building standalone, and also in Chromium - Adds a .gn and a build/BUILDCONFIG.gn that uses mini_chromium's build/BUILD.gn. - Adds some stub BUILD.gn files in locations where Chromium expects them (in //build, //testing, //third_party) containing empty targets/configs. These are no-ops in standalone builds, but add functionality when building in Chromium. This is in preference to having a global bool that conditionally does Chromium-y things in the Crashpad build files. These stub files are all contained in a secondary source root in build/chromium_compatibility, referred to by //.gn. - Adds //base/BUILD.gn which forwards to mini_chromium/base. This is only used when building standalone so that both Chromium and Crashpad can refer to it as "//base". - Changes references to other Crashpad targets to be relatively specified so that they work when the root of the project is //, and also when it's //third_party/crashpad/crashpad as it is in Chromium. - Moves any error-causing Mac/Win-specific files into explicit if (is_mac) or if (is_win) blocks as part of removing the dependency on set_sources_assignment_filter(). As yet unresolved: - CRASHPAD_IN_CHROMIUM needs to be removed when standalone; to be tackled in a follow up. - Not sure what to do with zlib yet, the build file currently assumes "in Chromium" too, and similarly having Crashpad //third_party/zlib:zlib pointing at itself doesn't work. Bug: crashpad:79 Change-Id: I6a7dda214e4b3b14a60c1ed285267ab97432a1a8 Reviewed-on: https://chromium-review.googlesource.com/777410 Reviewed-by: Mark Mentovai <mark@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-28 10:31:13 -08:00
"../client",
"../compat",
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
]
}
gn: add templates for executables and loadable_modules When building in chromium, executables and loadable_modules should depend on: //build/config:exe_and_shlib_deps which, among other things, may be needed to introduce a dependency on a custom libc++. Bug: crashpad:30 Change-Id: Ic46a3cf5b46bdac09cca22950f9236e0776ba44a Reviewed-on: https://chromium-review.googlesource.com/974713 Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-03-21 19:18:07 -07:00
crashpad_executable("crashpad_snapshot_test_crashing_child") {
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
testonly = true
Reformat all gn files Port of chromium-side https://chromium-review.googlesource.com/c/chromium/src/+/1997899 Bug: chromium:1041419 Change-Id: Ic7afefa0dea024da37fe4bb0f965840a160e2166 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2015428 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2020-01-23 08:00:33 -05:00
sources = [ "win/crashpad_snapshot_test_crashing_child.cc" ]
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
deps = [
ios: Update XCUITests to check various crash type exception codes. Bug: crashpad:31 Change-Id: I804def3be0050b3e6f15d7d77d0b70184c380673 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3087722 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2021-10-28 17:02:27 -04:00
"$mini_chromium_source_parent:base",
Rework GN files to start to support building standalone, and also in Chromium - Adds a .gn and a build/BUILDCONFIG.gn that uses mini_chromium's build/BUILD.gn. - Adds some stub BUILD.gn files in locations where Chromium expects them (in //build, //testing, //third_party) containing empty targets/configs. These are no-ops in standalone builds, but add functionality when building in Chromium. This is in preference to having a global bool that conditionally does Chromium-y things in the Crashpad build files. These stub files are all contained in a secondary source root in build/chromium_compatibility, referred to by //.gn. - Adds //base/BUILD.gn which forwards to mini_chromium/base. This is only used when building standalone so that both Chromium and Crashpad can refer to it as "//base". - Changes references to other Crashpad targets to be relatively specified so that they work when the root of the project is //, and also when it's //third_party/crashpad/crashpad as it is in Chromium. - Moves any error-causing Mac/Win-specific files into explicit if (is_mac) or if (is_win) blocks as part of removing the dependency on set_sources_assignment_filter(). As yet unresolved: - CRASHPAD_IN_CHROMIUM needs to be removed when standalone; to be tackled in a follow up. - Not sure what to do with zlib yet, the build file currently assumes "in Chromium" too, and similarly having Crashpad //third_party/zlib:zlib pointing at itself doesn't work. Bug: crashpad:79 Change-Id: I6a7dda214e4b3b14a60c1ed285267ab97432a1a8 Reviewed-on: https://chromium-review.googlesource.com/777410 Reviewed-by: Mark Mentovai <mark@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-28 10:31:13 -08:00
"../client",
"../compat",
"../util",
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
]
}
gn: add templates for executables and loadable_modules When building in chromium, executables and loadable_modules should depend on: //build/config:exe_and_shlib_deps which, among other things, may be needed to introduce a dependency on a custom libc++. Bug: crashpad:30 Change-Id: Ic46a3cf5b46bdac09cca22950f9236e0776ba44a Reviewed-on: https://chromium-review.googlesource.com/974713 Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-03-21 19:18:07 -07:00
crashpad_executable("crashpad_snapshot_test_dump_without_crashing") {
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
testonly = true
Reformat all gn files Port of chromium-side https://chromium-review.googlesource.com/c/chromium/src/+/1997899 Bug: chromium:1041419 Change-Id: Ic7afefa0dea024da37fe4bb0f965840a160e2166 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2015428 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2020-01-23 08:00:33 -05:00
sources = [ "win/crashpad_snapshot_test_dump_without_crashing.cc" ]
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
deps = [
ios: Update XCUITests to check various crash type exception codes. Bug: crashpad:31 Change-Id: I804def3be0050b3e6f15d7d77d0b70184c380673 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3087722 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2021-10-28 17:02:27 -04:00
"$mini_chromium_source_parent:base",
Rework GN files to start to support building standalone, and also in Chromium - Adds a .gn and a build/BUILDCONFIG.gn that uses mini_chromium's build/BUILD.gn. - Adds some stub BUILD.gn files in locations where Chromium expects them (in //build, //testing, //third_party) containing empty targets/configs. These are no-ops in standalone builds, but add functionality when building in Chromium. This is in preference to having a global bool that conditionally does Chromium-y things in the Crashpad build files. These stub files are all contained in a secondary source root in build/chromium_compatibility, referred to by //.gn. - Adds //base/BUILD.gn which forwards to mini_chromium/base. This is only used when building standalone so that both Chromium and Crashpad can refer to it as "//base". - Changes references to other Crashpad targets to be relatively specified so that they work when the root of the project is //, and also when it's //third_party/crashpad/crashpad as it is in Chromium. - Moves any error-causing Mac/Win-specific files into explicit if (is_mac) or if (is_win) blocks as part of removing the dependency on set_sources_assignment_filter(). As yet unresolved: - CRASHPAD_IN_CHROMIUM needs to be removed when standalone; to be tackled in a follow up. - Not sure what to do with zlib yet, the build file currently assumes "in Chromium" too, and similarly having Crashpad //third_party/zlib:zlib pointing at itself doesn't work. Bug: crashpad:79 Change-Id: I6a7dda214e4b3b14a60c1ed285267ab97432a1a8 Reviewed-on: https://chromium-review.googlesource.com/777410 Reviewed-by: Mark Mentovai <mark@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-28 10:31:13 -08:00
"../client",
"../compat",
"../util",
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
]
}
gn: add templates for executables and loadable_modules When building in chromium, executables and loadable_modules should depend on: //build/config:exe_and_shlib_deps which, among other things, may be needed to introduce a dependency on a custom libc++. Bug: crashpad:30 Change-Id: Ic46a3cf5b46bdac09cca22950f9236e0776ba44a Reviewed-on: https://chromium-review.googlesource.com/974713 Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-03-21 19:18:07 -07:00
crashpad_executable("crashpad_snapshot_test_extra_memory_ranges") {
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
testonly = true
Reformat all gn files Port of chromium-side https://chromium-review.googlesource.com/c/chromium/src/+/1997899 Bug: chromium:1041419 Change-Id: Ic7afefa0dea024da37fe4bb0f965840a160e2166 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2015428 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2020-01-23 08:00:33 -05:00
sources = [ "win/crashpad_snapshot_test_extra_memory_ranges.cc" ]
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
deps = [
ios: Update XCUITests to check various crash type exception codes. Bug: crashpad:31 Change-Id: I804def3be0050b3e6f15d7d77d0b70184c380673 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3087722 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2021-10-28 17:02:27 -04:00
"$mini_chromium_source_parent:base",
Rework GN files to start to support building standalone, and also in Chromium - Adds a .gn and a build/BUILDCONFIG.gn that uses mini_chromium's build/BUILD.gn. - Adds some stub BUILD.gn files in locations where Chromium expects them (in //build, //testing, //third_party) containing empty targets/configs. These are no-ops in standalone builds, but add functionality when building in Chromium. This is in preference to having a global bool that conditionally does Chromium-y things in the Crashpad build files. These stub files are all contained in a secondary source root in build/chromium_compatibility, referred to by //.gn. - Adds //base/BUILD.gn which forwards to mini_chromium/base. This is only used when building standalone so that both Chromium and Crashpad can refer to it as "//base". - Changes references to other Crashpad targets to be relatively specified so that they work when the root of the project is //, and also when it's //third_party/crashpad/crashpad as it is in Chromium. - Moves any error-causing Mac/Win-specific files into explicit if (is_mac) or if (is_win) blocks as part of removing the dependency on set_sources_assignment_filter(). As yet unresolved: - CRASHPAD_IN_CHROMIUM needs to be removed when standalone; to be tackled in a follow up. - Not sure what to do with zlib yet, the build file currently assumes "in Chromium" too, and similarly having Crashpad //third_party/zlib:zlib pointing at itself doesn't work. Bug: crashpad:79 Change-Id: I6a7dda214e4b3b14a60c1ed285267ab97432a1a8 Reviewed-on: https://chromium-review.googlesource.com/777410 Reviewed-by: Mark Mentovai <mark@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-28 10:31:13 -08:00
"../client",
"../compat",
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
]
}
gn: add templates for executables and loadable_modules When building in chromium, executables and loadable_modules should depend on: //build/config:exe_and_shlib_deps which, among other things, may be needed to introduce a dependency on a custom libc++. Bug: crashpad:30 Change-Id: Ic46a3cf5b46bdac09cca22950f9236e0776ba44a Reviewed-on: https://chromium-review.googlesource.com/974713 Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-03-21 19:18:07 -07:00
crashpad_executable("crashpad_snapshot_test_image_reader") {
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
testonly = true
Reformat all gn files Port of chromium-side https://chromium-review.googlesource.com/c/chromium/src/+/1997899 Bug: chromium:1041419 Change-Id: Ic7afefa0dea024da37fe4bb0f965840a160e2166 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2015428 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2020-01-23 08:00:33 -05:00
sources = [ "win/crashpad_snapshot_test_image_reader.cc" ]
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
deps = [
ios: Update XCUITests to check various crash type exception codes. Bug: crashpad:31 Change-Id: I804def3be0050b3e6f15d7d77d0b70184c380673 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3087722 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2021-10-28 17:02:27 -04:00
"$mini_chromium_source_parent:base",
Rework GN files to start to support building standalone, and also in Chromium - Adds a .gn and a build/BUILDCONFIG.gn that uses mini_chromium's build/BUILD.gn. - Adds some stub BUILD.gn files in locations where Chromium expects them (in //build, //testing, //third_party) containing empty targets/configs. These are no-ops in standalone builds, but add functionality when building in Chromium. This is in preference to having a global bool that conditionally does Chromium-y things in the Crashpad build files. These stub files are all contained in a secondary source root in build/chromium_compatibility, referred to by //.gn. - Adds //base/BUILD.gn which forwards to mini_chromium/base. This is only used when building standalone so that both Chromium and Crashpad can refer to it as "//base". - Changes references to other Crashpad targets to be relatively specified so that they work when the root of the project is //, and also when it's //third_party/crashpad/crashpad as it is in Chromium. - Moves any error-causing Mac/Win-specific files into explicit if (is_mac) or if (is_win) blocks as part of removing the dependency on set_sources_assignment_filter(). As yet unresolved: - CRASHPAD_IN_CHROMIUM needs to be removed when standalone; to be tackled in a follow up. - Not sure what to do with zlib yet, the build file currently assumes "in Chromium" too, and similarly having Crashpad //third_party/zlib:zlib pointing at itself doesn't work. Bug: crashpad:79 Change-Id: I6a7dda214e4b3b14a60c1ed285267ab97432a1a8 Reviewed-on: https://chromium-review.googlesource.com/777410 Reviewed-by: Mark Mentovai <mark@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-28 10:31:13 -08:00
"../client",
"../compat",
"../util",
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
]
gn: Fix symbol_level use in chromium style Bug: crashpad:79 Change-Id: I417f17194ee1a8ef157ea1e67e64878ccb6f5c10 Reviewed-on: https://chromium-review.googlesource.com/835528 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-12-19 17:15:10 -08:00
if (crashpad_is_in_chromium) {
if (symbol_level == 0) {
# The tests that use this executable rely on at least minimal debug
# info.
win, gn: use new lists when using templated targets The crashpad_{executable, loadable_module} templates won't have pre-existing configs lists to modify. Use configs and remove_configs to merge changes into default configs when using the templates. Change-Id: Id7c0b1991c9d0ac55022b427feb59df28668b959 Reviewed-on: https://chromium-review.googlesource.com/981778 Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-03-26 19:54:26 -07:00
remove_configs = [ "//build/config/compiler:default_symbols" ]
configs = [ "//build/config/compiler:minimal_symbols" ]
gn: Fix symbol_level use in chromium style Bug: crashpad:79 Change-Id: I417f17194ee1a8ef157ea1e67e64878ccb6f5c10 Reviewed-on: https://chromium-review.googlesource.com/835528 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-12-19 17:15:10 -08:00
}
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
}
}
gn: add templates for executables and loadable_modules When building in chromium, executables and loadable_modules should depend on: //build/config:exe_and_shlib_deps which, among other things, may be needed to introduce a dependency on a custom libc++. Bug: crashpad:30 Change-Id: Ic46a3cf5b46bdac09cca22950f9236e0776ba44a Reviewed-on: https://chromium-review.googlesource.com/974713 Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-03-21 19:18:07 -07:00
crashpad_loadable_module("crashpad_snapshot_test_image_reader_module") {
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
testonly = true
Reformat all gn files Port of chromium-side https://chromium-review.googlesource.com/c/chromium/src/+/1997899 Bug: chromium:1041419 Change-Id: Ic7afefa0dea024da37fe4bb0f965840a160e2166 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2015428 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2020-01-23 08:00:33 -05:00
sources = [ "win/crashpad_snapshot_test_image_reader_module.cc" ]
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
deps = [
[third_party] Make mini_chromium relocatable This will accommodate moving third_party/mini_chromium around. The default location is unchanged for now. There are GN variables that may need to be updated when Fuchsia's source re-organizes its layout: * mini_chromium_source_parent : this contains a BUILD.gn with groups and encloses the mini_chromium_source_root. This is controlled by the structure of the project that depends on this project. * _mini_chromium_source_root : this is what is normally checked out from git, the upstream source directory * mini_chromium_import_root : points inside source_root to make GN files accessible. This first step breaks out case logic for "if (crashpad_is_in_fuchsia)" even if the value is unchanged for now. This will faciliate a smaller change when Fuchsia re-structures third_party sources. Change-Id: I09e5362f4be8fdb440e3891422881b1053052341 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3062424 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Mark Mentovai <mark@chromium.org>
2021-07-28 23:57:54 +00:00
"$mini_chromium_source_parent:base",
ios: Update XCUITests to check various crash type exception codes. Bug: crashpad:31 Change-Id: I804def3be0050b3e6f15d7d77d0b70184c380673 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3087722 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2021-10-28 17:02:27 -04:00
"../client",
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
]
gn: Fix symbol_level use in chromium style Bug: crashpad:79 Change-Id: I417f17194ee1a8ef157ea1e67e64878ccb6f5c10 Reviewed-on: https://chromium-review.googlesource.com/835528 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-12-19 17:15:10 -08:00
if (crashpad_is_in_chromium) {
if (symbol_level == 0) {
# The tests that use this module rely on at least minimal debug info.
win, gn: use new lists when using templated targets The crashpad_{executable, loadable_module} templates won't have pre-existing configs lists to modify. Use configs and remove_configs to merge changes into default configs when using the templates. Change-Id: Id7c0b1991c9d0ac55022b427feb59df28668b959 Reviewed-on: https://chromium-review.googlesource.com/981778 Reviewed-by: Mark Mentovai <mark@chromium.org>
2018-03-26 19:54:26 -07:00
remove_configs = [ "//build/config/compiler:default_symbols" ]
configs = [ "//build/config/compiler:minimal_symbols" ]
gn: Fix symbol_level use in chromium style Bug: crashpad:79 Change-Id: I417f17194ee1a8ef157ea1e67e64878ccb6f5c10 Reviewed-on: https://chromium-review.googlesource.com/835528 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-12-19 17:15:10 -08:00
}
Upstream lightly modified Chromium BUILD.gn files Unreferenced, and not working at all in Crashpad-standalone. Copied from Chromium at 52a9831d81f2099ef9f50fcdaca5853019262c35 to have a point where a roll back into Chromium should be a no-op (with Chromium's build/secondary/third_party/crashpad/... removed). I'm not sure what we want to do about the various gni references into Chromium (e.g. //build/config/sanitizers/sanitizers.gni, //testing/test.gni, etc.) but I guess the sooner they live in Crashpad rather than in Chromium the sooner we can figure out the sort of knobs and dials we need. Bug: crashpad:79 Change-Id: Id99c29123bcd4174ee2bcc128c2be87e3c94fa3f Reviewed-on: https://chromium-review.googlesource.com/777819 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org>
2017-11-17 17:48:22 -08:00
}
}
}
Reference in New Issue Copy Permalink