Age | Commit message (Collapse) | Author |
|
am: 6ea7417777
Change-Id: I395e92856609753f068a68f92efe3632a4e79c09
|
|
am: dfc348fb2b
Change-Id: I154df01ea4c44b538235c2a6dc133474dfd00654
|
|
libdl is part of system_shared_libs now. -ldl -lpthread -lm are now defaults
for host_ldlibs on Linux and Darwin. -lrt is a default for host_ldlibs on
Linux.
Test: m host
Test: objdump -x out/host/linux-x86/lib64/libunwind.so
Test: nm -a out/host/linux-x86/lib64/libunwind.so | grep __CTOR_END__
Change-Id: I1ae950ef49f741d4df649405449d01f3f16f8ef1
|
|
f868a31f16 am: 27c9315e6c -s ours
am: fe8be1e7a3 -s ours
Change-Id: Id3676dcf137152507528073cd1ae3aa5352189d0
|
|
am: 27c9315e6c -s ours
Change-Id: Iac43a35ba34ffe48ba82f7d6fc1ecf08df2671ea
|
|
am: f868a31f16
Change-Id: Ia432cbae2b086b1006299cb7b95dbb0e7e6e31f9
|
|
am: 98996149c9
Change-Id: Ie47833d72ae4d56608dd2451e6ab92b8284bee56
|
|
As a VNDK/VNDK-SP module, Android.bp must have 'vndk' tag as well
as 'vendor_available: true'.
For a VNDK module, the 'vndk' tag has 'enabled: true'.
It will be installed system/lib(64)/vndk as a vendor variant.
For a VNDK-SP module, the 'vndk' tag has
'support_system_process: true' as well as 'enabled: true'.
It will be installed system/lib(64)/vndk-sp as a vendor variant.
Bug: 63866913
Test: build and boot with BOARD_VNDK_VERSION=current
Merged-In: I4517a3995efa91afb7fa21cdc0bc0fb8b088149b
Change-Id: I4517a3995efa91afb7fa21cdc0bc0fb8b088149b
(cherry picked from commit 50103091feb278697c922c91e097e924753fef9a)
|
|
819 snap-temp-L17400000090293341
Change-Id: I7f18bdf3b33bd50f11395d1a336bfa8421009f12
|
|
8d222cd40c am: e1b95886e2
am: 85ec116a32
Change-Id: I6e0ac3d3bd9cc300c56eea42875aa96e508552d3
|
|
8d222cd40c
am: e1b95886e2
Change-Id: I0e8ccab4919e422d344ed34fce8bb3b81b1d1378
|
|
am: 8d222cd40c
Change-Id: I67608072a9309cbf325071c006a1d517e8583d3b
|
|
am: 6c5b3c3fed
Change-Id: Id5010c945118920f54086d1a58ba2a671fe6b06f
|
|
am: 332513d0d2
Change-Id: I2832823edc5f85e3308f44e306b285aa83d094cc
|
|
Bug: N/A
Test: builds
Change-Id: I7d55b0b33cc44861ef22450afe68d421bde3f57a
Signed-off-by: Ivan Maidanski <i.maidanski@samsung.com>
|
|
208 snap-temp-L10800000088711883
Change-Id: Id845c84760c6161c14563f43c407183a7c00e02e
|
|
am: d010ccceba
Change-Id: Ic0d89bd84d04c599b5f523d8f023e72fa74a220f
|
|
am: 50103091fe
Change-Id: Id7c293c2a98017b50c52cfd322c6339a455a9516
|
|
As a VNDK/VNDK-SP module, Android.bp must have 'vndk' tag as well
as 'vendor_available: true'.
For a VNDK module, the 'vndk' tag has 'enabled: true'.
It will be installed system/lib(64)/vndk as a vendor variant.
For a VNDK-SP module, the 'vndk' tag has
'support_system_process: true' as well as 'enabled: true'.
It will be installed system/lib(64)/vndk-sp as a vendor variant.
Bug: 63866913
Test: build and boot with BOARD_VNDK_VERSION=current
Change-Id: I4517a3995efa91afb7fa21cdc0bc0fb8b088149b
|
|
am: 3d5ff8ecfa
Change-Id: If9c5eda9b3348bbacba66aea8d2db9d35827d7fb
|
|
am: 3169fc88c8
Change-Id: Ie4057e507eee470c3e0759b23287b7f78c95c818
|
|
am: 7162c82740
Change-Id: I73739fa39a5d4b2b54ccc09b63f1b030e0eee8b6
|
|
am: 76a0b9f6a9
Change-Id: I91f3f953eb9dd26ba7d010dcdecf6b4c9d3e5a31
|
|
The arg pointer is not really a struct cursor*, so skip the check altogether
and do the checks if CONSERVATIVE_CHECKS is defined.
Bug: 62350406
Test: Built art and ran test/testrunner/testrunner.py -b --host -t 137
Test: after removing the known failure. Verified before the fix, the test
Test: fails and after the fix, the test passes.
Change-Id: I4c9999e3292e469cb96080192027a2fc5ef9c857
|
|
e5e4c49907 am: 1c444ad862
am: 005d9401da
Change-Id: I66c9354f7360def6a1225f77fc5a2748b13b7d09
|
|
e5e4c49907
am: 1c444ad862
Change-Id: I896f8868e70395fca3ff9ac2649fb8ede6893ff1
|
|
am: e5e4c49907
Change-Id: I9f06803d1d1b18036d0a7e1993746e1a36f96837
|
|
am: adfc0a1a32
Change-Id: I27766bd2683bf4b968ffbcfc99dbd65dd152d468
|
|
Soong is changing to prepend architecture specific include directories
to the shared include directories. This breaks libunwind, which
expects to find include/libunwind_i.h before
include/tdep-<arch>/libunwind_i.h. To keep the includes in the right
order, pass "include" as an architecture specific include for every
architecture.
Test: mega device build
Change-Id: I71626492c9b853414d853cd02de832fd30333896
|
|
am: bb8d41b644
Change-Id: I2e6c7c495aed4451845374f9febf989ddbba10e1
|
|
am: f4c419ec42
Change-Id: Ibcc7c6f8a49efa551242d1b0548003ba4ac00293
|
|
am: 59e32437b0
Change-Id: I8db722b3646bf9284e0747f19f9ce26c170f198a
|
|
am: 0bda927d40
Change-Id: I2cf3f524d7951bb3eb9d53233169a88cd373fe07
|
|
am: 8d643497ec
Change-Id: I4cd9f0de9296c5295482704ec9063e19ae5695cd
|
|
am: 5626fc0816
Change-Id: I43f162d74bc6e4d3eb3b681c86dc45f89c545e12
|
|
By setting vendor_available, the following may become true:
* a prebuilt library from this release may be used at runtime by
in a later releasse (by vendor code compiled against this release).
so this library shouldn't depend on runtime state that may change
in the future.
* this library may be loaded twice into a single process (potentially
an old version and a newer version). The symbols will be isolated
using linker namespaces, but this may break assumptions about 1
library in 1 process (your singletons will run twice).
Background:
This means that these modules may be built and installed twice --
once for the system partition and once for the vendor partition. The
system version will build just like today, and will be used by the
framework components on /system. The vendor version will build
against a reduced set of exports and libraries -- similar to, but
separate from, the NDK. This means that all your dependencies must
also mark vendor_available.
At runtime, /system binaries will load libraries from /system/lib*,
while /vendor binaries will load libraries from /vendor/lib*. There
are some exceptions in both directions -- bionic(libc,etc) and liblog
are always loaded from /system. And SP-HALs (OpenGL, etc) may load
/vendor code into /system processes, but the dependencies of those
libraries will load from /vendor until it reaches a library that's
always on /system. In the SP-HAL case, if both framework and vendor
libraries depend on a library of the same name, both versions will be
loaded, but they will be isolated from each other.
It's possible to compile differently -- reducing your source files,
exporting different include directories, etc. For details see:
https://android-review.googlesource.com/368372
None of this is enabled unless the device opts into the system/vendor
split with BOARD_VNDK_VERSION := current.
Bug: 36426473
Bug: 36079834
Test: Android-aosp_arm.mk is the same before/after
Test: build.ninja is the same before/after
Test: build-aosp_arm.ninja is the same before/after
Test: attempt to compile with BOARD_VNDK_VERSION := current
Merged-In: Ic1c1cfdab14bb24dfb93b6a1ba3d6443e1e3e67e
Change-Id: Ic1c1cfdab14bb24dfb93b6a1ba3d6443e1e3e67e
|
|
By setting vendor_available, the following may become true:
* a prebuilt library from this release may be used at runtime by
in a later releasse (by vendor code compiled against this release).
so this library shouldn't depend on runtime state that may change
in the future.
* this library may be loaded twice into a single process (potentially
an old version and a newer version). The symbols will be isolated
using linker namespaces, but this may break assumptions about 1
library in 1 process (your singletons will run twice).
Background:
This means that these modules may be built and installed twice --
once for the system partition and once for the vendor partition. The
system version will build just like today, and will be used by the
framework components on /system. The vendor version will build
against a reduced set of exports and libraries -- similar to, but
separate from, the NDK. This means that all your dependencies must
also mark vendor_available.
At runtime, /system binaries will load libraries from /system/lib*,
while /vendor binaries will load libraries from /vendor/lib*. There
are some exceptions in both directions -- bionic(libc,etc) and liblog
are always loaded from /system. And SP-HALs (OpenGL, etc) may load
/vendor code into /system processes, but the dependencies of those
libraries will load from /vendor until it reaches a library that's
always on /system. In the SP-HAL case, if both framework and vendor
libraries depend on a library of the same name, both versions will be
loaded, but they will be isolated from each other.
It's possible to compile differently -- reducing your source files,
exporting different include directories, etc. For details see:
https://android-review.googlesource.com/368372
None of this is enabled unless the device opts into the system/vendor
split with BOARD_VNDK_VERSION := current.
Bug: 36426473
Bug: 36079834
Test: Android-aosp_arm.mk is the same before/after
Test: build.ninja is the same before/after
Test: build-aosp_arm.ninja is the same before/after
Test: attempt to compile with BOARD_VNDK_VERSION := current
Change-Id: Ic1c1cfdab14bb24dfb93b6a1ba3d6443e1e3e67e
|
|
am: f4f32399ac
Change-Id: I59593e600d6fbf5b6b4d837ca8cb5e4dfa640b2a
|
|
am: b9d4549100
Change-Id: I8e3542d04c42e3d22cd7c2b2ca216c52d3c14cc6
|
|
am: 1b47da733e
Change-Id: I39329e0ba582b8f949c4743385a8534b27ca7b4b
|
|
Bug: 34468756
Test: Wrote a new test in system/core/libbacktrace that passes with
Test: this fix. Ran all of the other backtrace unit tests.
Change-Id: I0be65192f85f05593738a4d3f00c3a2b95d69df5
|
|
am: a51e64dfde
Change-Id: Ic7130d8ff4a487571a6953c84d845fcb1f099acf
|
|
am: f7eef920b5
Change-Id: I626d94bcfeee703f9c783c0f8eced9d11666995d
|
|
The struct unw_addr_space is very large (at least 13624 bytes on arm),
but is on the stack in the function map_create_list.
Allocate this function when needed instead of putting it on the stack.
Bug: 33293182
Test: Built and ran backtrace_test on an angler. Stepped through the
Test: modified code and verified it is called and allocated properly.
Test: Ran valgrind on the backtrace_test.local_trace to verify that
Test: the memory is not leaked.
Change-Id: I298e72d6b87d2701111c4659c46246b308f275e9
(cherry picked from commit 50270d3ef2127372c0ae6aefd9be255ab901f573)
|
|
am: 591a2eb3f3
Change-Id: Iefda17599fdb15481510536bd0d1bc3d103b763e
|
|
am: 2a286501e6
Change-Id: Ib5c82ce3b35ae8fce54619f14dc1c4bbf1edb3f1
|
|
am: de858ed3a4
Change-Id: I71229f73fd10d8ffeee6322fd81738a9c1e6900a
|
|
am: 50270d3ef2
Change-Id: Ic8b2336685c848287defe0826b73875f849ba2a5
|
|
The struct unw_addr_space is very large (at least 13624 bytes on arm),
but is on the stack in the function map_create_list.
Allocate this function when needed instead of putting it on the stack.
Bug: 33293182
Test: Built and ran backtrace_test on an angler. Stepped through the
Test: modified code and verified it is called and allocated properly.
Test: Ran valgrind on the backtrace_test.local_trace to verify that
Test: the memory is not leaked.
Change-Id: I298e72d6b87d2701111c4659c46246b308f275e9
|
|
am: 67b6f15b0c
Change-Id: Ic0614304a19441ac1ed81eda77f11eec233e1af4
|