commit | 50321e2e66f19998970e59d666bc9af387345b3a | [log] [tgz] |
---|---|---|
author | Pavel Chupin <pavel.v.chupin@intel.com> | Fri Sep 26 16:02:09 2014 +0400 |
committer | Elliott Hughes <enh@google.com> | Mon Oct 27 16:14:55 2014 -0700 |
tree | 32f70c79741c7fbe2ce68ce36e9d0907cba26d95 | |
parent | ec58e29b276b0f98eb624430fb70703dc32057bf [diff] |
[x86,x86_64] Fix libgcc unwinding through signal This change provides __restore/__restore_rt on x86 and __restore_rt on x86_64 with unwinding information to be able to unwind through signal frame via libgcc provided unwinding interface. See comments inlined for more details. Also remove the test that had a dependency on __attribute__((cleanup(foo_cleanup))). It doesn't provide us with any better test coverage than we have from the newer tests, and it doesn't work well across a variety architectures (presumably because no one uses this attribute in the real world). Tested this on host via bionic-unit-tests-run-on-host on both x86 and x86-64. Bug: 17436734 Change-Id: I2f06814e82c8faa732cb4f5648868dc0fd2e5fe4 Signed-off-by: Pavel Chupin <pavel.v.chupin@intel.com>
The C library. Stuff like fopen(3)
and kill(2)
.
The math library. Traditionally Unix systems kept stuff like sin(3)
and cos(3)
in a separate library to save space in the days before shared libraries.
The dynamic linker interface library. This is actually just a bunch of stubs that the dynamic linker replaces with pointers to its own implementation at runtime. This is where stuff like dlopen(3)
lives.
The C++ ABI support functions. The C++ compiler doesn't know how to implement thread-safe static initialization and the like, so it just calls functions that are supplied by the system. Stuff like __cxa_guard_acquire
and __cxa_pure_virtual
live here.
The dynamic linker. When you run a dynamically-linked executable, its ELF file has a DT_INTERP
entry that says “use the following program to start me”. On Android, that‘s either linker
or linker64
(depending on whether it’s a 32-bit or 64-bit executable). It's responsible for loading the ELF executable into memory and resolving references to symbols (so that when your code tries to jump to fopen(3)
, say, it lands in the right place).
The tests/
directory contains unit tests. Roughly arranged as one file per publicly-exported header file.
The benchmarks/
directory contains benchmarks.
Adding a system call usually involves:
As mentioned above, this is currently a two-step process:
This is fully automated:
The tests are all built from the tests/ directory.
$ mma $ adb sync $ adb shell /data/nativetest/bionic-unit-tests/bionic-unit-tests32 $ adb shell \ /data/nativetest/bionic-unit-tests-static/bionic-unit-tests-static32 # Only for 64-bit targets $ adb shell /data/nativetest/bionic-unit-tests/bionic-unit-tests64 $ adb shell \ /data/nativetest/bionic-unit-tests-static/bionic-unit-tests-static64
The host tests require that you have lunch
ed either an x86 or x86_64 target.
$ mma # 64-bit tests for 64-bit targets, 32-bit otherwise. $ mm bionic-unit-tests-run-on-host # Only exists for 64-bit targets. $ mm bionic-unit-tests-run-on-host32
As a way to check that our tests do in fact test the correct behavior (and not just the behavior we think is correct), it is possible to run the tests against the host's glibc.
$ mma $ bionic-unit-tests-glibc32 # already in your path $ bionic-unit-tests-glibc64
For either host or target coverage, you must first:
$ export NATIVE_COVERAGE=true
bionic_coverage=true
in libc/Android.mk
and libm/Android.mk
.$ mma $ adb sync $ adb shell \ GCOV_PREFIX=/data/local/tmp/gcov \ GCOV_PREFIX_STRIP=`echo $ANDROID_BUILD_TOP | grep -o / | wc -l` \ /data/nativetest/bionic-unit-tests/bionic-unit-tests32 $ acov
acov
will pull all coverage information from the device, push it to the right directories, run lcov
, and open the coverage report in your browser.
First, build and run the host tests as usual (see above).
$ croot $ lcov -c -d $ANDROID_PRODUCT_OUT -o coverage.info $ genhtml -o covreport coverage.info # or lcov --list coverage.info
The coverage report is now available at covreport/index.html
.