Lines Matching refs:that

19 Our general practice with dynamic linker behavior changes is that they
27 * Warnings about any behavior change that will affect a library if you
28 increase your target API level will appear in logcat when that library
29 is loaded, even if you're not yet targeting that API level.
32 as toasts. Experience has shown that many developers don’t habitually
40 on the dynamic linker's search path. This meant that apps
65 in that order. For API 23 and later, for any given library, the dynamic
72 the local group. This allows ASAN, for example, to ensure that it can
78 LD_PRELOAD applies to both 32- and 64-bit processes. This means that you
87 correctly in API 23 and later. Note that RTLD_LOCAL is the default,
88 so even calls to dlopen(3) that didn’t explicitly use RTLD_LOCAL will
98 above. (Use --hash-style=both if you want to build code that uses this
108 releases would assume that the basename of the library was the soname,
109 and used that to search for already-loaded libraries. For example,
112 that it was impossible to have two libraries `"dir1/libx.so"` and
118 machine’s file system) that used to work because we ignored everything
127 library so that old code gets the old version and new code gets the new
137 at install time. This meant that they took up space in your APK and
140 that you want to load directly from your APK must be page aligned
144 Note that in API level 23 and above dlopen(3) will open a library from
162 handle platform changes. For that reason, we recommend against using
164 Compatibility Test Suite (CTS) that all Android devices must pass. They
165 may not exist, or they may behave differently. This makes apps that use
171 a set of libraries that see significant use from Google Play's
172 most-installed apps, and that are feasible for us to support in the
175 temporarily support these libraries; so if you see a warning that means
179 used to deny access to the greylist even to an app that would normally
233 *Resolution*: remove the extra steps from your build that strip section
257 the TEXTREL entry declares that the .so contains text relocations). This
269 you're not generating ELF files that claim to have text relocations,
288 absolute paths, that doesn't make sense on Android because you have
298 it is not present in that exact location on the device.
300 Even worse, some build systems have bugs that cause them to insert
301 DT_NEEDED entries that point to a file on the build host, something that
315 library using the path specified, and that path won't exist on the
316 device. There are broken third-party toolchains/build systems that use
340 are not found, or you try to use an ABI-incompatible library that isn't
344 default. Ensure you're using the current NDK and that you haven't
353 that is built with a target API level >= 23 therefore will not load on earlier
356 *Resolution*: build your code with an NDK target API level that matches your
371 Each segment in an ELF file has associated flags that tell the
374 writable. This means that the W (for Writable) and E (for Executable)
383 *Resolution*: we're aware of one middleware product that introduces these
397 *Resolution*: don't use tools that produce invalid/malformed
398 ELF files. Note that using them puts application under high risk of
413 of libraries. Note also that `dlerror` doesn't correspond to actual
436 Not calling `dlclose` or ensuring that your library has `RTLD_NODELETE`
437 set (so that calls to `dlclose` don't actually unload the library)
455 Most apps should be unaffected by this change, but apps that hook or try to