Shared libraries are not found when running a rank on a Xeon Phi™ coprocessor.
error while loading shared libraries: lib*.so: cannot open shared object file: No such file or directory
When launching a job running in either native or symmetric mode, ranks launched on Xeon Phi" coprocessors under the LSF* job scheduler will not correctly set LD_LIBRARY_PATH. Instead, the default LD_LIBRARY_PATH for the coprocessor will be used. If shared libraries are located in other locations, they will not be found.
The Sampling Enabling Product (SEP) is a powerful tool for collecting event based profiling data on a system. SEP uses a hardware based, low-overhead and system-wide collector that helps identify the modules and functions that are consuming the most time. This article discusses several techniques that we have found useful when troubleshooting issues with SEP.
In troubleshooting SEP issues on embedded Linux* systems, there are several steps you should take:
As there are currently no public engineering devices from Intel, we will work with two images for emulated targets (Note: Please refer to http://source.android.com/source/initializing.html and http://source.android.com/source/downloading.html for the details. The pages help to resolve common problems with tools and environment. You may need to have a Google account.): the target QEMU-based emulator and the target for VirtualBox.
Android* applications can incorporate native code using the Native Development Kit (NDK) toolset. It allows developers to reuse legacy code, code to low-level hardware, or differentiate their applications by taking advantage of features otherwise not optimal or possible.
The challenges and approaches to identifying runtime issues and possible problem code in an Android* OS–targeted application or in the Android* system software stack is going to be remarkably similar, regardless of whether the underlying platform architecture is based on Intel® architecture and the latest generation Intel® Atom™ processor or on ARM* architecture. In this chapter we will provide an overview of the available debug methodologies for Android*-targeted software debug on Intel architecture.
1 Supported Operating Systems
The following operating systems are supported:
• Windows XP* (32-bit), Vista* (32- or 64-bit), or Windows 7* (32- or 64-bit)
• Mac OSX* (32- or 64-bit)
• Linux* (Ubuntu, Fedora); GNU C Library (glibc) 2.7 or later is required.
• On Ubuntu Linux, version 8.04 or later is required.
• On Fedora, target versions are F-12 and higher.
• 64-bit distributions must be capable of running 32-bit applications.