User Guide


Search Directories for Android* Targets

For accurate module resolution and source analysis of your Android* application, make sure to specify search paths for binary and source files when configuring performance analysis:
If you have not set the project search directories at the time of collection or import, you will not be able to open the source code. Only Assembly view will be available for source analysis.
Consider the following when adding search paths:
  • By default, the
    pulls many binaries from the target device.
  • The Kernel
    is one file that does not contain symbols on the target device. Typically it is located in
    [AndroidOSBuildDir]/out/target/product/[your target]/linux/kernel/vmlinux
  • Many operating system binaries with symbols are located in either
    your target
    , or
    your target
  • Application binaries with symbols are located in
  • Application source files for the C/C++ modules are usually located in
    , not in
    (where the Java *source files are). Some third-party software in Android does not provide binaries with symbols. You must contact the third party to get a version of the binaries with symbols.
  • You can see if a binary has symbols by using the
    command in Linux and make sure that it says
    not stripped
    file MyBinary.ext MyBinary.ext: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, not stripped

Product and Performance Information


Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804