chromium-src-build/asan.saves

24 строки
689 B
Plaintext
Исходник Обычный вид История

Revert of Reland https://codereview.chromium.org/298333007/: Enable mac_strip_release under ASan on OSX. Remo… (patchset #1 id:1 of https://codereview.chromium.org/517803004/) Reason for revert: Breaks *lots* of browser_tests on Mac ASan. See e.g.: http://build.chromium.org/p/chromium.memory/buildstatus?builder=Mac%20ASan%2064%20Tests%20%281%29&number=2036 http://build.chromium.org/p/chromium.memory/buildstatus?builder=Mac%20ASan%2064%20Tests%20%282%29&number=2600 http://build.chromium.org/p/chromium.memory/buildstatus?builder=Mac%20ASan%2064%20Tests%20%283%29&number=2424 Original issue's description: > Reland https://codereview.chromium.org/298333007/: Enable mac_strip_release under ASan on OSX. Remove the .saves files. > > The reasons for reverting the CL hadn't been documented. I'm going to reland and update the bugs. > > Unce upon a time the ASan runtime library used to be statically linked into > the executables on OSX. > Because that library provided a number of API functions needed by the shared > libraries, we had custom ASan-specific .saves files that told the `strip` > utility to preserve those functions when stripping the executables. > > Then ASan switched to using dynamic runtime library, which instantly broke the > stripping step, because the executables weren't necessarily referencing all the > ASan API functions (issue 242503). > As a result, stripping has been disabled, and we haven't had .dSYM debug info > for ASan builds for more than a year now (issue 148383). > > Because the ASan API functions are now undefined in the executables, it's > actually senseless to use the .saves files to preserve those functions. > This CL deletes the .saves files and turns mac_strip_release on for ASan > builds. > > BUG=148383, 242503, 170739, 166857 > TBR=mark@chromium.org > > Committed: https://chromium.googlesource.com/chromium/src/+/d5319a149964f953e7506c1ff2b33f90974d19ea TBR=mark@chromium.org,glider@chromium.org NOTREECHECKS=true NOTRY=true BUG=148383, 242503, 170739, 166857 Review URL: https://codereview.chromium.org/522743003 Cr-Original-Commit-Position: refs/heads/master@{#292885} Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src Cr-Mirrored-Commit: 0b804d0007f4fc6b6d99f699e160819ab90c1798
2014-09-01 21:06:48 +04:00
# Copyright (c) 2011 The Chromium Authors. All rights reserved.
# Use of this source code is governed by a BSD-style license that can be
# found in the LICENSE file.
Revert of Another attempt to fix debug info stripping for ASan on OSX (patchset #5 id:80001 of https://codereview.chromium.org/560323004/) Reason for revert: Broke mac asan content_browsertests: http://build.chromium.org/p/chromium.memory/builders/Mac%20ASan%20Tests%20%281%29/builds/4311/steps/content_browsertests/logs/stdio Original issue's description: > Another attempt to fix debug info stripping for ASan on OSX > > Unce upon a time the ASan runtime library used to be statically linked into > the executables on OSX. > Because that library provided a number of API functions needed by the shared > libraries, we had custom ASan-specific .saves files that told the `strip` > utility to preserve those functions when stripping the executables. > > Then ASan switched to using dynamic runtime library, which instantly broke the > stripping step, because the executables weren't necessarily referencing all the > ASan API functions (issue 242503). > As a result, stripping has been disabled, and we haven't had .dSYM debug info > for ASan builds for more than a year now (issue 148383). > > Because the ASan API functions are now undefined in the executables, it's > actually senseless to use the .saves files to preserve those functions in each > executable. However __asan_default_options still must be preserved to be accessible > from the ASan runtime. > > This CL removes all ASan symbols except for __asan_default_options from the .saves files > and makes Chromium.app and Chromium Helper.app correctly use app_asan.saves. > It also turns mac_strip_release on for ASan builds. > > BUG=148383,242503,170739,166857 > R=mark@chromium.org > TBR=cpu@chromium.org > > Committed: https://crrev.com/d051b21c75afc414190db331fd608cc61e3056dc > Cr-Commit-Position: refs/heads/master@{#296413} TBR=mark@chromium.org,cpu@chromium.org,glider@chromium.org NOTREECHECKS=true NOTRY=true BUG=148383,242503,170739,166857 Review URL: https://codereview.chromium.org/597873004 Cr-Original-Commit-Position: refs/heads/master@{#296434} Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src Cr-Mirrored-Commit: 55c7faab2f0ce87d91d4cb995a41bb260210e773
2014-09-24 20:25:18 +04:00
# This file lists symbols that should not be stripped by Xcode from the binaries
# built for Mac OS X using AddressSanitizer
Revert of Reland https://codereview.chromium.org/298333007/: Enable mac_strip_release under ASan on OSX. Remo… (patchset #1 id:1 of https://codereview.chromium.org/517803004/) Reason for revert: Breaks *lots* of browser_tests on Mac ASan. See e.g.: http://build.chromium.org/p/chromium.memory/buildstatus?builder=Mac%20ASan%2064%20Tests%20%281%29&number=2036 http://build.chromium.org/p/chromium.memory/buildstatus?builder=Mac%20ASan%2064%20Tests%20%282%29&number=2600 http://build.chromium.org/p/chromium.memory/buildstatus?builder=Mac%20ASan%2064%20Tests%20%283%29&number=2424 Original issue's description: > Reland https://codereview.chromium.org/298333007/: Enable mac_strip_release under ASan on OSX. Remove the .saves files. > > The reasons for reverting the CL hadn't been documented. I'm going to reland and update the bugs. > > Unce upon a time the ASan runtime library used to be statically linked into > the executables on OSX. > Because that library provided a number of API functions needed by the shared > libraries, we had custom ASan-specific .saves files that told the `strip` > utility to preserve those functions when stripping the executables. > > Then ASan switched to using dynamic runtime library, which instantly broke the > stripping step, because the executables weren't necessarily referencing all the > ASan API functions (issue 242503). > As a result, stripping has been disabled, and we haven't had .dSYM debug info > for ASan builds for more than a year now (issue 148383). > > Because the ASan API functions are now undefined in the executables, it's > actually senseless to use the .saves files to preserve those functions. > This CL deletes the .saves files and turns mac_strip_release on for ASan > builds. > > BUG=148383, 242503, 170739, 166857 > TBR=mark@chromium.org > > Committed: https://chromium.googlesource.com/chromium/src/+/d5319a149964f953e7506c1ff2b33f90974d19ea TBR=mark@chromium.org,glider@chromium.org NOTREECHECKS=true NOTRY=true BUG=148383, 242503, 170739, 166857 Review URL: https://codereview.chromium.org/522743003 Cr-Original-Commit-Position: refs/heads/master@{#292885} Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src Cr-Mirrored-Commit: 0b804d0007f4fc6b6d99f699e160819ab90c1798
2014-09-01 21:06:48 +04:00
# (http://dev.chromium.org/developers/testing/addresssanitizer).
Revert of Another attempt to fix debug info stripping for ASan on OSX (patchset #5 id:80001 of https://codereview.chromium.org/560323004/) Reason for revert: Broke mac asan content_browsertests: http://build.chromium.org/p/chromium.memory/builders/Mac%20ASan%20Tests%20%281%29/builds/4311/steps/content_browsertests/logs/stdio Original issue's description: > Another attempt to fix debug info stripping for ASan on OSX > > Unce upon a time the ASan runtime library used to be statically linked into > the executables on OSX. > Because that library provided a number of API functions needed by the shared > libraries, we had custom ASan-specific .saves files that told the `strip` > utility to preserve those functions when stripping the executables. > > Then ASan switched to using dynamic runtime library, which instantly broke the > stripping step, because the executables weren't necessarily referencing all the > ASan API functions (issue 242503). > As a result, stripping has been disabled, and we haven't had .dSYM debug info > for ASan builds for more than a year now (issue 148383). > > Because the ASan API functions are now undefined in the executables, it's > actually senseless to use the .saves files to preserve those functions in each > executable. However __asan_default_options still must be preserved to be accessible > from the ASan runtime. > > This CL removes all ASan symbols except for __asan_default_options from the .saves files > and makes Chromium.app and Chromium Helper.app correctly use app_asan.saves. > It also turns mac_strip_release on for ASan builds. > > BUG=148383,242503,170739,166857 > R=mark@chromium.org > TBR=cpu@chromium.org > > Committed: https://crrev.com/d051b21c75afc414190db331fd608cc61e3056dc > Cr-Commit-Position: refs/heads/master@{#296413} TBR=mark@chromium.org,cpu@chromium.org,glider@chromium.org NOTREECHECKS=true NOTRY=true BUG=148383,242503,170739,166857 Review URL: https://codereview.chromium.org/597873004 Cr-Original-Commit-Position: refs/heads/master@{#296434} Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src Cr-Mirrored-Commit: 55c7faab2f0ce87d91d4cb995a41bb260210e773
2014-09-24 20:25:18 +04:00
___asan_init
___asan_handle_no_return
___asan_register_global
___asan_register_globals
___asan_unregister_globals
___asan_report_load1
___asan_report_load2
___asan_report_load4
___asan_report_load8
___asan_report_load16
___asan_report_store1
___asan_report_store2
___asan_report_store4
___asan_report_store8
___asan_report_store16