| commit | 52db0eb46c52fa9b993f419b7d4796c9687ab0cf | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Oct 14 11:20:07 2016 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Oct 14 15:56:13 2016 +0000 |
| tree | c2023373a43847b87b34592b4fc115f6c0f06e9c | |
| parent | 4c0e6c64b6866926f96576bc8e8ea8849f018159 [diff] |
Revert "Get the malloc tests working under ASan." This reverts commit 7b9bbd9639727a97bfea513cc1f2ad0a36f845ca. This seems to cause some problem linking with gold in Chromium: ../../third_party/binutils/Linux_x64/Release/bin/ld.gold: warning: Cannot export local symbol 'free' ../../third_party/binutils/Linux_x64/Release/bin/ld.gold: warning: Cannot export local symbol 'malloc' ../../third_party/binutils/Linux_x64/Release/bin/ld.gold: warning: Cannot export local symbol 'realloc' ../../third_party/binutils/Linux_x64/Release/bin/ld.gold: error: treating warnings as errors The same error in https://crbug.com/368351 implies we're actually causing the compiler to make some assumptions it shouldn't make. The obvious fix of marking things as visible causes crashes when built with ASan (ASan's malloc interceptors and ours are conflicting somehow). Revert this for now. We should study how ASan's interceptors work and figure out how to make these two coexist. BUG=655938 Change-Id: Iaad245d1028c442bd924d46519b20115d37a57c4 Reviewed-on: https://boringssl-review.googlesource.com/11604 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.
Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability.
Programs ship their own copies of BoringSSL when they use it and we update everything as needed when deciding to make API changes. This allows us to mostly avoid compromises in the name of compatibility. It works for us, but it may not work for you.
BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google's product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily.
Currently BoringSSL is the SSL library in Chrome/Chromium, Android (but it's not part of the NDK) and a number of other apps/programs.
There are other files in this directory which might be helpful: