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/compat/compat.gyp

147 lines
3.7 KiB
Plaintext
Raw Normal View History

Add compat to Crashpad. compat includes headers providing definitions normally provided by the system, in cases where the system SDK does not always provide the correct or up-to-date definitions, and cases where code on different platforms needs to access definitions normally only available on one platform. To provide definitions on a single platform, where the system SDK may not provide the definitions correctly, use subdirectories named for the platform, such as “mac”. To provide definitions normally available on only one platform to others, use subdirectories that identify that they are to be used on platforms other than the one that originated their definitions, such as “non_win”. In all cases, headers should be named as they are natively in their respective SDKs, so that it’s possible to #include them according to their usual names. R=rsesek@chromium.org Review URL: https://codereview.chromium.org/432843002
2014-07-31 13:45:51 -04:00
# Copyright 2014 The Crashpad Authors. All rights reserved.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
{
Set the chromium_code GYP variable. When building in the Chromium tree, chromium_code is necessary to apply Chromium’s build/filename_rules.gypi. Crashpad’s build depends on these rules. chromium_code also enables a high warning level, which is desirable for Crashpad. BUG=crashpad:12 R=rsesek@chromium.org Review URL: https://codereview.chromium.org/986873002
2015-03-08 15:17:22 -04:00
'includes': [
'../build/crashpad.gypi',
],
Add compat to Crashpad. compat includes headers providing definitions normally provided by the system, in cases where the system SDK does not always provide the correct or up-to-date definitions, and cases where code on different platforms needs to access definitions normally only available on one platform. To provide definitions on a single platform, where the system SDK may not provide the definitions correctly, use subdirectories named for the platform, such as “mac”. To provide definitions normally available on only one platform to others, use subdirectories that identify that they are to be used on platforms other than the one that originated their definitions, such as “non_win”. In all cases, headers should be named as they are natively in their respective SDKs, so that it’s possible to #include them according to their usual names. R=rsesek@chromium.org Review URL: https://codereview.chromium.org/432843002
2014-07-31 13:45:51 -04:00
'targets': [
{
Set target_name on many targets to use a crashpad_ prefix. In Chromium, many targets are built, sharing a single output directory. Collisions are likely. When integrating Crashpad into Chromium, the ui/snapshot library and Crashpad’s snapshot library were found to conflict. This change gives most Crashpad targets a “crashpad_” prefix to avoid conflicts. All library and test targets are given a target_name with this prefix. Existing tools are not likely to conflict with anything else and are not given a prefix. BUG=crashpad:12 R=rsesek@chromium.org, scottmg@chromium.org Review URL: https://codereview.chromium.org/990553003
2015-03-08 16:25:34 -04:00
'target_name': 'crashpad_compat',
linux, mac: disable cfi-icall for cross-dso calls CFI attempts to verify that the dynamic type of a function object matches the static type of the function pointer used to call it. https://clang.llvm.org/docs/ControlFlowIntegrity.html#indirect-function-call-checking However, the analyzer does not have enough information to check cross-dso calls. In these instances, CFI crashes upon calling the function with an error like: pthread_create_linux.cc:60:16: runtime error: control flow integrity check for type 'int (unsigned long *, const pthread_attr_t *, void *(*)(void *), void *)' failed during indirect function call (/lib/x86_64-linux-gnu/libpthread.so.0+0x9200): note: (unknown) defined here pthread_create_linux.cc:60:16: note: check failed in crashpad_handler, destination function located in /lib/x86_64-linux-gnu/libpthread.so.0 Change-Id: Ib29dabfe714f2ee9cc06a5d17e6899ff81a06df4 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2339332 Commit-Queue: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2020-09-10 14:23:59 -07:00
'dependencies': [
'../util/no_cfi_icall.gyp:no_cfi_icall',
],
'include_dirs': [
'..',
],
Add compat to Crashpad. compat includes headers providing definitions normally provided by the system, in cases where the system SDK does not always provide the correct or up-to-date definitions, and cases where code on different platforms needs to access definitions normally only available on one platform. To provide definitions on a single platform, where the system SDK may not provide the definitions correctly, use subdirectories named for the platform, such as “mac”. To provide definitions normally available on only one platform to others, use subdirectories that identify that they are to be used on platforms other than the one that originated their definitions, such as “non_win”. In all cases, headers should be named as they are natively in their respective SDKs, so that it’s possible to #include them according to their usual names. R=rsesek@chromium.org Review URL: https://codereview.chromium.org/432843002
2014-07-31 13:45:51 -04:00
'sources': [
android: add Dlsym() which wraps `dlsym` `dlsym` on Android KitKat (4.4.*) raises SIGFPE when searching for non-existent symbols. This wrapper installs a signal handler prior to calling `dlsym`. Bug: crashpad:30 Change-Id: Iee94672d3c11b1fad1b01526eea7df688c0356cb Reviewed-on: https://chromium-review.googlesource.com/835411 Commit-Queue: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2017-12-22 15:32:37 -08:00
'android/dlfcn_internal.cc',
'android/dlfcn_internal.h',
linux/android: List compat headers in compat.gyp One more for Windows too: compat/win/sys/time.h. Bug: crashpad:30 Change-Id: I1f11933a5937a65db10774d0710d44dc85f8586a Reviewed-on: https://chromium-review.googlesource.com/705278 Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2017-10-06 12:47:28 -04:00
'android/elf.h',
'android/linux/elf.h',
'android/linux/prctl.h',
'android/linux/ptrace.h',
'android/sched.h',
linux: Add ExceptionHandlerServer and ExceptionHandlerClient Bug: crashpad:30 Change-Id: I60874a26ccb281144f870df2b4d16c6970a39f6b Reviewed-on: https://chromium-review.googlesource.com/772824 Commit-Queue: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2017-12-19 12:03:54 -08:00
'android/sys/epoll.cc',
'android/sys/epoll.h',
android: Fix 32-bit test to build at API [21, 24) with unified headers Although API 21 introduced support for 64-bit off_t in many system calls or their wrappers, <stdio.h> support for 64-bit off_t is absent until API 24. This is a partial revert of 5969d6b1eb22, because with this more targeted fix applying only to gtest, the rest of Crashpad will work with a 64-bit off_t even at API levels lacking NDK support by going through the mmap() shim in compat. This includes a mini_chromium update to 96e32dd499a4. 85cbec19ffc0 fuchsia: Make EINTR macros no-ops fbf410cd4d40 fuchsia: Use koid instead of getpid() for process field in logging 96e32dd499a4 Revert "android: Don’t use _FILE_OFFSET_BITS=64 until API 21" Bug: crashpad:211 Change-Id: I34c3c8b42eb315605e6775962b44c3c4573b7462 Reviewed-on: https://chromium-review.googlesource.com/811204 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2017-12-06 12:53:54 -05:00
'android/sys/mman.h',
android: Fix “gn analyze” On Android, the compat library built compat/android/sys/mman.cc, which provides a fallback for mmap, and compat/linux/sys/mman.cc, which provides a fallback for memfd_create. This can result in two object files colliding in the library, which is flagged as a “gn analyze” error: > ERROR at //crashpad/compat/BUILD.gn:62:5: Duplicate object file > static_library(target_name) { > ^---------------------------- > The target //crashpad/compat:compat > generates two object files with the same name: > obj/crashpad/compat/compat/mman.o > > It could be you accidentally have a file listed twice in the > sources. Or, depending on how your toolchain maps sources to > object files, two source files with the same name in different > directories could map to the same object file. > > In the latter case, either rename one of the files or move one of > the sources to a separate source_set to avoid them both being in > the same target. The files are renamed to avoid this collision. The associated headers cannot be renamed because they need to shadow the SDK’s copies. There is no “gn analyze” conflict reported for headers with the same name. Change-Id: Ia49ef5ff8375673395597e96555f72f7c69e3564 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2285965 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org>
2020-07-08 00:00:18 -04:00
'android/sys/mman_mmap.cc',
linux/android: List compat headers in compat.gyp One more for Windows too: compat/win/sys/time.h. Bug: crashpad:30 Change-Id: I1f11933a5937a65db10774d0710d44dc85f8586a Reviewed-on: https://chromium-review.googlesource.com/705278 Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2017-10-06 12:47:28 -04:00
'android/sys/syscall.h',
'android/sys/user.h',
'linux/signal.h',
'linux/sys/ptrace.h',
Alias user regs structs for glibc ARM64 pre 2.20 Change-Id: Ie8e4ce8df34c4d14e874884db50d748d03af9592 Reviewed-on: https://chromium-review.googlesource.com/1117644 Reviewed-by: Scott Graham <scottmg@chromium.org> Commit-Queue: Joshua Peraza <jperaza@chromium.org>
2018-06-27 14:07:25 -07:00
'linux/sys/user.h',
mac: Switch from <AvailabilityMacros.h> to <Availability.h> The macOS 11.0 SDK, as of Xcode 12b6 12A8189n, has not updated <AvailabilityMacros.h> with a MAC_OS_X_VERSION_11_0 or MAC_OS_X_VERSION_10_16 constant. However, the <Availability.h> interface has been updated to provide both __MAC_11_0 and __MAC_10_16. <AvailabilityMacros.h>’s MAC_OS_X_VERSION_MAX_ALLOWED, which is supposed to identify the SDK version, is broken in the 11.0 SDK in that whenever the deployment target is set to 10.15 or earlier, the SDK will be mis-identified through this interface as 10.15. When using the <Availability.h> equivalent, __MAC_OS_X_VERSION_MAX_ALLOWED, the 11.0 SDK is identified as 10.16 (arguably it should be internally versioned as 11.0, but at least this interface allows it to be detected unambiguously.) It’s clear that the <AvailabilityMacros.h> interface provides no meaningful support for the macOS 11.0 SDK at all, but <Availability.h> does. <Availability.h> was introduced in the Mac OS X 10.5 SDK, so there is no relevant SDK version compatibility problem with this interface. Key differences between these interfaces for the purposes used by Crashpad: - <AvailabilityMacros.h> → <Availability.h> - MAC_OS_X_VERSION_MIN_REQUIRED (DT) → __MAC_OS_X_VERSION_MIN_REQUIRED - MAC_OS_X_VERSION_MAX_ALLOWED (SDK) → __MAC_OS_X_VERSION_MAX_ALLOWED - MAC_OS_X_VERSION_x_y → __MAC_x_y - <Availability.h> __MAC_OS_X_VERSION_* SDK/DT macros are only available when targeting macOS, while <AvailabilityMacros.h> MAC_OS_X_VERSION_* SDK/DT macros are available on all Apple platforms, which may be a source of confusion. (<Availability.h> __MAC_* macros do remain available on all Apple platforms.) This change was made mostly mechanically by: sed -i '' -Ee 's/<AvailabilityMacros.h>/<Availability.h>/g' \ $(git grep -E -l '<AvailabilityMacros.h>' | grep -v AvailabilityMacros.h) sed -i '' -Ee 's/(MAC_OS_X_VERSION_(MIN_REQUIRED|MAX_ALLOWED))/__\1/g' \ $(git grep -E -l 'MAC_OS_X_VERSION_(MIN_REQUIRED|MAX_ALLOWED)' | grep -v AvailabilityMacros.h) sed -i '' -Ee 's/(MAC_OS_X_VERSION_(10_[0-9]+))/__MAC_\2/g' \ $(git grep -E -l 'MAC_OS_X_VERSION_(10_[0-9]+)' | grep -v AvailabilityMacros.h) Bug: crashpad:347 Change-Id: Ibdcd7a6215a82f7060b7b67d98691f88454085fc Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2382421 Reviewed-by: Robert Sesek <rsesek@chromium.org> Commit-Queue: Mark Mentovai <mark@chromium.org>
2020-08-28 20:00:15 -04:00
'mac/Availability.h',
'mac/AvailabilityVersions.h',
Add missing comma in compat.gyp Causes a warning in the gyp-msvs generator. R=mark@chromium.org Review URL: https://codereview.chromium.org/1490073005 .
2015-12-02 15:31:44 -08:00
'mac/kern/exc_resource.h',
mac: Provide a larger thread state buffer for AVX-512 on 10.13 Crashpad doesn’t use AVX-512, but when receiving replies to exceptions forwarded to ReportCrash, may see buffers large enough to contain AVX-512 thread state. This can result in messages like “UniversalExceptionRaise: (ipc/rcv) msg too large (0x10004004)”. I386_THREAD_STATE_MAX has increased from 224 to 614 in the 10.13 SDK, meaning that the maximum supported size for old_state and new_state in [mach_]exception_raise_state[_identity]() has increased from 896 to 2,456 bytes. This constant defines the size of the buffer that these MIG-generated routines will work with. By providing this definition in compat, the buffer size is increased when building with older SDKs. Note that on the “send” side, the size of the message given to mach_msg() will be trimmed to include only the valid part of the state area based on the stateCnt field, so increasing the value to 614 here won’t result Crashpad sending messages this large. That would be a potential interoperability concern with older OS versions. Bug: crashpad:185, crashpad:190 Change-Id: Ia46091ae46fd6227a17f59eb4bc00914be471aa7 Reviewed-on: https://chromium-review.googlesource.com/541515 Reviewed-by: Robert Sesek <rsesek@chromium.org>
2017-06-20 09:50:37 -04:00
'mac/mach/i386/thread_state.h',
Add compat to Crashpad. compat includes headers providing definitions normally provided by the system, in cases where the system SDK does not always provide the correct or up-to-date definitions, and cases where code on different platforms needs to access definitions normally only available on one platform. To provide definitions on a single platform, where the system SDK may not provide the definitions correctly, use subdirectories named for the platform, such as “mac”. To provide definitions normally available on only one platform to others, use subdirectories that identify that they are to be used on platforms other than the one that originated their definitions, such as “non_win”. In all cases, headers should be named as they are natively in their respective SDKs, so that it’s possible to #include them according to their usual names. R=rsesek@chromium.org Review URL: https://codereview.chromium.org/432843002
2014-07-31 13:45:51 -04:00
'mac/mach/mach.h',
'mac/mach-o/loader.h',
Accept non-fatal resource exceptions without generating crash reports. This adds IsExceptionNonfatalResource() and its test, and uses it in crashpad_handler. When non-fatal resource exceptions are encountered, no crash report is generated. crashpad_handler swallows these exceptions. Alternatively, it could allow them to be sent to the system’s host-level resource exception handler, normally com.apple.ReportCrash.root, which would allow them to be processed in the same way as when Crashpad is not in use. I’m not sure which option is better. I chose to swallow them because there doesn’t appear to be much value in letting com.apple.ReportCrash.root and spindump look at them. This also moves ExcCrashRecoverOriginalException() to the new file as a sibling of IsExceptionNonfatalResource(). This provides better organization. BUG=crashpad:35, chromium:474163, chromium:474326 TEST=crashpad_util_test ExceptionTypes.IsExceptionNonfatalResource R=rsesek@chromium.org Review URL: https://codereview.chromium.org/1066243002
2015-04-08 17:46:09 -04:00
'mac/sys/resource.h',
Add minidump_extensions.h, which defines Crashpad/Breakpad extensions to the standard minidump format defined in dbghelp.h. R=rsesek@chromium.org Review URL: https://codereview.chromium.org/435013002
2014-08-01 14:37:20 -04:00
'non_mac/mach/mach.h',
Add compat to Crashpad. compat includes headers providing definitions normally provided by the system, in cases where the system SDK does not always provide the correct or up-to-date definitions, and cases where code on different platforms needs to access definitions normally only available on one platform. To provide definitions on a single platform, where the system SDK may not provide the definitions correctly, use subdirectories named for the platform, such as “mac”. To provide definitions normally available on only one platform to others, use subdirectories that identify that they are to be used on platforms other than the one that originated their definitions, such as “non_win”. In all cases, headers should be named as they are natively in their respective SDKs, so that it’s possible to #include them according to their usual names. R=rsesek@chromium.org Review URL: https://codereview.chromium.org/432843002
2014-07-31 13:45:51 -04:00
'non_win/dbghelp.h',
'non_win/minwinbase.h',
'non_win/timezoneapi.h',
'non_win/verrsrc.h',
win: Work towards getting 'minidump' to compile - dbghelp.h requires windows.h to be included before it (ick!). Add a stub one for non_win to make this work. - convert __attribute__ -> macro that can work work with MSVC; - a handful of narrowing casts. R=mark@chromium.org BUG=crashpad:1 Review URL: https://codereview.chromium.org/883773005
2015-02-04 17:30:03 -08:00
'non_win/windows.h',
Add compat to Crashpad. compat includes headers providing definitions normally provided by the system, in cases where the system SDK does not always provide the correct or up-to-date definitions, and cases where code on different platforms needs to access definitions normally only available on one platform. To provide definitions on a single platform, where the system SDK may not provide the definitions correctly, use subdirectories named for the platform, such as “mac”. To provide definitions normally available on only one platform to others, use subdirectories that identify that they are to be used on platforms other than the one that originated their definitions, such as “non_win”. In all cases, headers should be named as they are natively in their respective SDKs, so that it’s possible to #include them according to their usual names. R=rsesek@chromium.org Review URL: https://codereview.chromium.org/432843002
2014-07-31 13:45:51 -04:00
'non_win/winnt.h',
win: get tools/crashpad_database_util mostly working - Add public domain getopt implementation to third_party. - Add timegm to compat/win. - Add stub of strptime to compat/win. Requires https://codereview.chromium.org/1119173003/ and https://codereview.chromium.org/1117013006/. Rather than working in wchar_t everywhere on Windows, convert UTF16 command line arguments in wmain to UTF8, work primarily in UTF8, and convert back when necessary to UTF16 for base::FilePath. This avoids the need to genericize over all the standard C string functions, getopt, etc. while still handling non-ASCII properly. R=mark@chromium.org BUG=crashpad:1 Review URL: https://codereview.chromium.org/1119783005
2015-05-06 10:28:07 -07:00
'win/getopt.h',
win: Provide strcasecmp() in <strings.h> in compat. base::strcasecmp() has been deprecated since upstream 8a800901b78a2. BUG=chromium:472900 R=rsesek@chromium.org Review URL: https://codereview.chromium.org/1275633002 .
2015-08-05 16:34:50 -04:00
'win/strings.cc',
'win/strings.h',
linux/android: List compat headers in compat.gyp One more for Windows too: compat/win/sys/time.h. Bug: crashpad:30 Change-Id: I1f11933a5937a65db10774d0710d44dc85f8586a Reviewed-on: https://chromium-review.googlesource.com/705278 Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2017-10-06 12:47:28 -04:00
'win/sys/time.h',
win: Add compat header for sys/types.h To add definition of ssize_t. Uses #include <../include/...> to emulate #include_next, similar to the mac headers. BUG=crashpad:1 R=mark@chromium.org Review URL: https://codereview.chromium.org/793013002
2014-12-10 11:39:50 -08:00
'win/sys/types.h',
win: get tools/crashpad_database_util mostly working - Add public domain getopt implementation to third_party. - Add timegm to compat/win. - Add stub of strptime to compat/win. Requires https://codereview.chromium.org/1119173003/ and https://codereview.chromium.org/1117013006/. Rather than working in wchar_t everywhere on Windows, convert UTF16 command line arguments in wmain to UTF8, work primarily in UTF8, and convert back when necessary to UTF16 for base::FilePath. This avoids the need to genericize over all the standard C string functions, getopt, etc. while still handling non-ASCII properly. R=mark@chromium.org BUG=crashpad:1 Review URL: https://codereview.chromium.org/1119783005
2015-05-06 10:28:07 -07:00
'win/time.cc',
'win/time.h',
win: Expect uneven symbolic link support As mentioned at https://chromium-review.googlesource.com/c/chromium/src/+/735820#message-e8b199498d8b850f2612c46648069d819dd47517, the typical Windows behavior for symbolic links requires administrative privileges. Symbolic links are available to non-administrators in Windows 10.0.15063 and later (1703, Creators Update), provided that developer mode has been enabled and SYMBOLIC_LINK_FLAG_ALLOW_UNPRIVILEGED_CREATE is passed to CreateSymbolicLink(). See https://blogs.windows.com/buildingapps/2016/12/02/symlinks-windows-10/. This adds SYMBOLIC_LINK_FLAG_ALLOW_UNPRIVILEGED_CREATE to uses of CreateSymbolicLink(), and creates test::CanCreateSymbolicLinks() to determine whether symbolic link creation is possible. Tests that exercise symbolic links are adapted to gate all symbolic link operations on this test. Test: crashpad_util_test DirectoryReader.*:Filesystem.* Change-Id: I8250cadd974ffcc7abe32701a0d5bc487061baf0 Bug: crashpad: Reviewed-on: https://chromium-review.googlesource.com/739472 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-10-26 18:37:49 -04:00
'win/winbase.h',
win: Add implementation of system_snapshot for Windows ProcessReaderWin only a stub for now. R=mark@chromium.org BUG=crashpad:1 Review URL: https://codereview.chromium.org/936333004
2015-03-02 13:06:34 -08:00
'win/winnt.h',
win: 10.0.16299.0 SDK compatibility This corresponds to Windows 10 version 1709 (Fall Creators Update, “Redstone 3”). While compiling util/win/nt_internals.cc: …\crashpad\crashpad\util\win\nt_internals.cc(22): error C2371: 'CLIENT_ID': redefinition; different basic types c:\program files (x86)\windows kits\10\include\10.0.16299.0\um\winternl.h(83): note: see declaration of 'CLIENT_ID' The CLIENT_ID structure, which should have been part of the SDK to begin with, has been added. Provide a compatible definition in <winternl.h>. Bug: chromium:773476 Change-Id: Iafc77f8cffd06d1194fc909bad587f1ffd1687a2 Reviewed-on: https://chromium-review.googlesource.com/711415 Reviewed-by: Leonard Mosescu <mosescu@chromium.org> Commit-Queue: Mark Mentovai <mark@chromium.org>
2017-10-11 00:19:13 -04:00
'win/winternl.h',
Add compat to Crashpad. compat includes headers providing definitions normally provided by the system, in cases where the system SDK does not always provide the correct or up-to-date definitions, and cases where code on different platforms needs to access definitions normally only available on one platform. To provide definitions on a single platform, where the system SDK may not provide the definitions correctly, use subdirectories named for the platform, such as “mac”. To provide definitions normally available on only one platform to others, use subdirectories that identify that they are to be used on platforms other than the one that originated their definitions, such as “non_win”. In all cases, headers should be named as they are natively in their respective SDKs, so that it’s possible to #include them according to their usual names. R=rsesek@chromium.org Review URL: https://codereview.chromium.org/432843002
2014-07-31 13:45:51 -04:00
],
10.6 SDK compatibility. TEST=util_test MachOImageReader.* (and all others with a 10.6 SDK build) R=rsesek@chromium.org Review URL: https://codereview.chromium.org/561933004
2014-09-12 12:13:27 -04:00
'conditions': [
['OS=="mac"', {
compat.gyp: use type=none for header-only target On Linux and macOS, compat.gyp:crashpad_compat is a header-only target, which should be declared type=none. This CL also adds the missing non_mac/ include_dirs for non-macOS targets. Bug: crashpad: Change-Id: I7bef32e8f6bdcb86f51118a1bb1d3b52d05120d1 Reviewed-on: https://chromium-review.googlesource.com/1124773 Reviewed-by: Joshua Peraza <jperaza@chromium.org> Commit-Queue: Joshua Peraza <jperaza@chromium.org>
2018-07-03 15:01:12 -04:00
'type': 'none',
10.6 SDK compatibility. TEST=util_test MachOImageReader.* (and all others with a 10.6 SDK build) R=rsesek@chromium.org Review URL: https://codereview.chromium.org/561933004
2014-09-12 12:13:27 -04:00
'include_dirs': [
'mac',
],
'direct_dependent_settings': {
'include_dirs': [
'mac',
],
},
compat.gyp: use type=none for header-only target On Linux and macOS, compat.gyp:crashpad_compat is a header-only target, which should be declared type=none. This CL also adds the missing non_mac/ include_dirs for non-macOS targets. Bug: crashpad: Change-Id: I7bef32e8f6bdcb86f51118a1bb1d3b52d05120d1 Reviewed-on: https://chromium-review.googlesource.com/1124773 Reviewed-by: Joshua Peraza <jperaza@chromium.org> Commit-Queue: Joshua Peraza <jperaza@chromium.org>
2018-07-03 15:01:12 -04:00
}, {
'include_dirs': [
'non_mac',
],
'direct_dependent_settings': {
'include_dirs': [
'non_mac',
],
},
10.6 SDK compatibility. TEST=util_test MachOImageReader.* (and all others with a 10.6 SDK build) R=rsesek@chromium.org Review URL: https://codereview.chromium.org/561933004
2014-09-12 12:13:27 -04:00
}],
win: Add compat header for sys/types.h To add definition of ssize_t. Uses #include <../include/...> to emulate #include_next, similar to the mac headers. BUG=crashpad:1 R=mark@chromium.org Review URL: https://codereview.chromium.org/793013002
2014-12-10 11:39:50 -08:00
['OS=="win"', {
compat.gyp: use type=none for header-only target On Linux and macOS, compat.gyp:crashpad_compat is a header-only target, which should be declared type=none. This CL also adds the missing non_mac/ include_dirs for non-macOS targets. Bug: crashpad: Change-Id: I7bef32e8f6bdcb86f51118a1bb1d3b52d05120d1 Reviewed-on: https://chromium-review.googlesource.com/1124773 Reviewed-by: Joshua Peraza <jperaza@chromium.org> Commit-Queue: Joshua Peraza <jperaza@chromium.org>
2018-07-03 15:01:12 -04:00
'type': 'static_library',
win: Add compat header for sys/types.h To add definition of ssize_t. Uses #include <../include/...> to emulate #include_next, similar to the mac headers. BUG=crashpad:1 R=mark@chromium.org Review URL: https://codereview.chromium.org/793013002
2014-12-10 11:39:50 -08:00
'include_dirs': [
'win',
],
'direct_dependent_settings': {
'include_dirs': [
'win',
],
},
win: get tools/crashpad_database_util mostly working - Add public domain getopt implementation to third_party. - Add timegm to compat/win. - Add stub of strptime to compat/win. Requires https://codereview.chromium.org/1119173003/ and https://codereview.chromium.org/1117013006/. Rather than working in wchar_t everywhere on Windows, convert UTF16 command line arguments in wmain to UTF8, work primarily in UTF8, and convert back when necessary to UTF16 for base::FilePath. This avoids the need to genericize over all the standard C string functions, getopt, etc. while still handling non-ASCII properly. R=mark@chromium.org BUG=crashpad:1 Review URL: https://codereview.chromium.org/1119783005
2015-05-06 10:28:07 -07:00
'dependencies': [
'../third_party/getopt/getopt.gyp:getopt',
],
win: Add compat header for sys/types.h To add definition of ssize_t. Uses #include <../include/...> to emulate #include_next, similar to the mac headers. BUG=crashpad:1 R=mark@chromium.org Review URL: https://codereview.chromium.org/793013002
2014-12-10 11:39:50 -08:00
}, {
10.6 SDK compatibility. TEST=util_test MachOImageReader.* (and all others with a 10.6 SDK build) R=rsesek@chromium.org Review URL: https://codereview.chromium.org/561933004
2014-09-12 12:13:27 -04:00
'include_dirs': [
'non_win',
],
'direct_dependent_settings': {
'include_dirs': [
'non_win',
],
},
}],
android: Support builds with NDK API versions older than 21 (compat) The new Linux ProcessInfo implementation uses two macros not readily available in NDK API versions older than 21 (Android 5.0.0): NT_PRSTATUS and PR_GETREGSET. Chrome uses API 21 for 64-bit builds, but uses API 16 for 32-bit builds. NT_PRSTATUS is normally defined by <elf.h> or by <linux/elf.h>, included by <elf.h>. Although the definition in <linux/elf.h> is available in older NDK API versions, this internal header does not mix well with <elf.h> unless <elf.h> contemplates this combination. As of NDK API 21, <elf.h> actually delegates most of its work to <linux/elf.h>. PR_GETREGSET is not available in the NDK at all until API 21. Its definition is in <linux/ptrace.h>. Most user code should #include <sys/ptrace.h> instead, which includes <linux/ptrace.h>. Bug: crashpad:30 Test: crashpad_util_test ProcessInfo.* Change-Id: I4d07a9964db4665a49bde490e905ae9126880bc5 Reviewed-on: https://chromium-review.googlesource.com/455659 Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2017-03-15 13:47:31 -04:00
['OS=="android"', {
compat.gyp: use type=none for header-only target On Linux and macOS, compat.gyp:crashpad_compat is a header-only target, which should be declared type=none. This CL also adds the missing non_mac/ include_dirs for non-macOS targets. Bug: crashpad: Change-Id: I7bef32e8f6bdcb86f51118a1bb1d3b52d05120d1 Reviewed-on: https://chromium-review.googlesource.com/1124773 Reviewed-by: Joshua Peraza <jperaza@chromium.org> Commit-Queue: Joshua Peraza <jperaza@chromium.org>
2018-07-03 15:01:12 -04:00
'type': 'static_library',
android: Support builds with NDK API versions older than 21 (compat) The new Linux ProcessInfo implementation uses two macros not readily available in NDK API versions older than 21 (Android 5.0.0): NT_PRSTATUS and PR_GETREGSET. Chrome uses API 21 for 64-bit builds, but uses API 16 for 32-bit builds. NT_PRSTATUS is normally defined by <elf.h> or by <linux/elf.h>, included by <elf.h>. Although the definition in <linux/elf.h> is available in older NDK API versions, this internal header does not mix well with <elf.h> unless <elf.h> contemplates this combination. As of NDK API 21, <elf.h> actually delegates most of its work to <linux/elf.h>. PR_GETREGSET is not available in the NDK at all until API 21. Its definition is in <linux/ptrace.h>. Most user code should #include <sys/ptrace.h> instead, which includes <linux/ptrace.h>. Bug: crashpad:30 Test: crashpad_util_test ProcessInfo.* Change-Id: I4d07a9964db4665a49bde490e905ae9126880bc5 Reviewed-on: https://chromium-review.googlesource.com/455659 Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2017-03-15 13:47:31 -04:00
'include_dirs': [
'android',
linux: Add ExceptionSnapshotLinux Bug: crashpad:30 Change-Id: I450d53a89af2995c0fd13b31821360e781fe015a Reviewed-on: https://chromium-review.googlesource.com/589747 Commit-Queue: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2017-08-01 19:05:06 -07:00
'linux',
android: Support builds with NDK API versions older than 21 (compat) The new Linux ProcessInfo implementation uses two macros not readily available in NDK API versions older than 21 (Android 5.0.0): NT_PRSTATUS and PR_GETREGSET. Chrome uses API 21 for 64-bit builds, but uses API 16 for 32-bit builds. NT_PRSTATUS is normally defined by <elf.h> or by <linux/elf.h>, included by <elf.h>. Although the definition in <linux/elf.h> is available in older NDK API versions, this internal header does not mix well with <elf.h> unless <elf.h> contemplates this combination. As of NDK API 21, <elf.h> actually delegates most of its work to <linux/elf.h>. PR_GETREGSET is not available in the NDK at all until API 21. Its definition is in <linux/ptrace.h>. Most user code should #include <sys/ptrace.h> instead, which includes <linux/ptrace.h>. Bug: crashpad:30 Test: crashpad_util_test ProcessInfo.* Change-Id: I4d07a9964db4665a49bde490e905ae9126880bc5 Reviewed-on: https://chromium-review.googlesource.com/455659 Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2017-03-15 13:47:31 -04:00
],
'direct_dependent_settings': {
'include_dirs': [
'android',
linux: Add ExceptionSnapshotLinux Bug: crashpad:30 Change-Id: I450d53a89af2995c0fd13b31821360e781fe015a Reviewed-on: https://chromium-review.googlesource.com/589747 Commit-Queue: Joshua Peraza <jperaza@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org>
2017-08-01 19:05:06 -07:00
'linux',
android: Support builds with NDK API versions older than 21 (compat) The new Linux ProcessInfo implementation uses two macros not readily available in NDK API versions older than 21 (Android 5.0.0): NT_PRSTATUS and PR_GETREGSET. Chrome uses API 21 for 64-bit builds, but uses API 16 for 32-bit builds. NT_PRSTATUS is normally defined by <elf.h> or by <linux/elf.h>, included by <elf.h>. Although the definition in <linux/elf.h> is available in older NDK API versions, this internal header does not mix well with <elf.h> unless <elf.h> contemplates this combination. As of NDK API 21, <elf.h> actually delegates most of its work to <linux/elf.h>. PR_GETREGSET is not available in the NDK at all until API 21. Its definition is in <linux/ptrace.h>. Most user code should #include <sys/ptrace.h> instead, which includes <linux/ptrace.h>. Bug: crashpad:30 Test: crashpad_util_test ProcessInfo.* Change-Id: I4d07a9964db4665a49bde490e905ae9126880bc5 Reviewed-on: https://chromium-review.googlesource.com/455659 Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2017-03-15 13:47:31 -04:00
],
},
android: Support mmap() with large file offsets and API < 21 Chrome (and therefore mini_chromium) has always built with _FILE_OFFSET_BITS=64, which is intended to enable a 64-bit off_t even for 32-bit programs. However, support was never present in Android with NDK traditional headers. The new NDK unified headers do recognize _FILE_OFFSET_BITS=64 and enable a 64-bit off_t, along with corresponding functions and system call wrappers. However, no mmap() wrapper supporting a 64-bit off_t for 32-bit programs was available prior to API 21 (Android 5.0 “Lollipop”), so when targeting older API levels, NDK headers do not proivde an mmap() declaration. This avoids silently truncating 64-bit off_t values to 32 bits. NDK r15b did make such an mmap() wrapper available (https://android.googlesource.com/platform/bionic/+/785b249df024), and it did silently truncate, but this was removed for r15c (https://android.googlesource.com/platform/bionic/+/00fedf587917). How should this work if _FILE_OFFSET_BITS is set to 64 and recent unified headers are in use? The strategy employed here is to provide an mmap() declaration in compat, with a 64-bit off_t. That mmap() will call to Bionic’s mmap64() wrapper if available (it’s available since Android 5.0 “Lollipop”). If unavailable, it implements the same logic that mmap64() does directly, which predominantly involves calling the __mmap2() system call. Bionic has always provided wrappers for __mmap2(). Additional reading: https://android.googlesource.com/platform/bionic/+/0bfcbaf4d069/docs/32-bit-abi.md#is-32_bit-1 https://github.com/android-ndk/ndk/issues/442 Bug: crashpad:30 Change-Id: I98c10e2eda773cb6f3d9eb8db9b8bfde43c885e7 Reviewed-on: https://chromium-review.googlesource.com/705674 Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2017-10-06 15:58:36 -04:00
'link_settings': {
'libraries': [
'-ldl',
],
},
android: Support builds with NDK API versions older than 21 (compat) The new Linux ProcessInfo implementation uses two macros not readily available in NDK API versions older than 21 (Android 5.0.0): NT_PRSTATUS and PR_GETREGSET. Chrome uses API 21 for 64-bit builds, but uses API 16 for 32-bit builds. NT_PRSTATUS is normally defined by <elf.h> or by <linux/elf.h>, included by <elf.h>. Although the definition in <linux/elf.h> is available in older NDK API versions, this internal header does not mix well with <elf.h> unless <elf.h> contemplates this combination. As of NDK API 21, <elf.h> actually delegates most of its work to <linux/elf.h>. PR_GETREGSET is not available in the NDK at all until API 21. Its definition is in <linux/ptrace.h>. Most user code should #include <sys/ptrace.h> instead, which includes <linux/ptrace.h>. Bug: crashpad:30 Test: crashpad_util_test ProcessInfo.* Change-Id: I4d07a9964db4665a49bde490e905ae9126880bc5 Reviewed-on: https://chromium-review.googlesource.com/455659 Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2017-03-15 13:47:31 -04:00
}],
linux: Use PTRACE_GET_THREAD_AREA for x86 ThreadInfo.GetThreadArea Linux supports TLS on x86 by allocating slots in the GDT, accessible via the system calls get/set_thread_area. This allows segment registers (%gs on x86) to be used to quickly access the TLS. Previously, we used PTRACE_GETREGSET with the NT_386_TLS regset. This "register set" provides access to the subarray of the GDT used for TLS. However, there are multiple slots provided and we don't know which one is being used by the threading library for the current thread's TLS. Previously, we were just using the first one, which worked for x86 on 64-bit kernels, but not 32-bit kernels. On 32-bit kernels, the first slot ended up pointing to the TLS of the main thread. The authoritative index of the current thread's TLS in the GDT is given by bits 3-15 of %gs. However, this index cannot be used with PTRACE_GETREGSET+NT386_TLS because we don't know the location of the TLS slots in the GDT. PTRACE_GET_THREAD_AREA, however, accepts an index from the start of the GDT similarly to get/set_thread_area. Bug: crashpad:30 Change-Id: Ie6dfbdd088c6816fad409812a1a97037d4b38fd7 Reviewed-on: https://chromium-review.googlesource.com/575318 Reviewed-by: Mark Mentovai <mark@chromium.org>
2017-07-18 16:42:58 -07:00
['OS=="linux"', {
compat.gyp: use type=none for header-only target On Linux and macOS, compat.gyp:crashpad_compat is a header-only target, which should be declared type=none. This CL also adds the missing non_mac/ include_dirs for non-macOS targets. Bug: crashpad: Change-Id: I7bef32e8f6bdcb86f51118a1bb1d3b52d05120d1 Reviewed-on: https://chromium-review.googlesource.com/1124773 Reviewed-by: Joshua Peraza <jperaza@chromium.org> Commit-Queue: Joshua Peraza <jperaza@chromium.org>
2018-07-03 15:01:12 -04:00
'type': 'none',
linux: Use PTRACE_GET_THREAD_AREA for x86 ThreadInfo.GetThreadArea Linux supports TLS on x86 by allocating slots in the GDT, accessible via the system calls get/set_thread_area. This allows segment registers (%gs on x86) to be used to quickly access the TLS. Previously, we used PTRACE_GETREGSET with the NT_386_TLS regset. This "register set" provides access to the subarray of the GDT used for TLS. However, there are multiple slots provided and we don't know which one is being used by the threading library for the current thread's TLS. Previously, we were just using the first one, which worked for x86 on 64-bit kernels, but not 32-bit kernels. On 32-bit kernels, the first slot ended up pointing to the TLS of the main thread. The authoritative index of the current thread's TLS in the GDT is given by bits 3-15 of %gs. However, this index cannot be used with PTRACE_GETREGSET+NT386_TLS because we don't know the location of the TLS slots in the GDT. PTRACE_GET_THREAD_AREA, however, accepts an index from the start of the GDT similarly to get/set_thread_area. Bug: crashpad:30 Change-Id: Ie6dfbdd088c6816fad409812a1a97037d4b38fd7 Reviewed-on: https://chromium-review.googlesource.com/575318 Reviewed-by: Mark Mentovai <mark@chromium.org>
2017-07-18 16:42:58 -07:00
'include_dirs': [
'linux',
],
'direct_dependent_settings': {
'include_dirs': [
'linux',
],
},
}],
10.6 SDK compatibility. TEST=util_test MachOImageReader.* (and all others with a 10.6 SDK build) R=rsesek@chromium.org Review URL: https://codereview.chromium.org/561933004
2014-09-12 12:13:27 -04:00
],
Add compat to Crashpad. compat includes headers providing definitions normally provided by the system, in cases where the system SDK does not always provide the correct or up-to-date definitions, and cases where code on different platforms needs to access definitions normally only available on one platform. To provide definitions on a single platform, where the system SDK may not provide the definitions correctly, use subdirectories named for the platform, such as “mac”. To provide definitions normally available on only one platform to others, use subdirectories that identify that they are to be used on platforms other than the one that originated their definitions, such as “non_win”. In all cases, headers should be named as they are natively in their respective SDKs, so that it’s possible to #include them according to their usual names. R=rsesek@chromium.org Review URL: https://codereview.chromium.org/432843002
2014-07-31 13:45:51 -04:00
},
],
}
Reference in New Issue Copy Permalink