summaryrefslogtreecommitdiff
path: root/libc/malloc_debug/malloc_debug.cpp
diff options
context:
space:
mode:
authorJiyong Park <jiyong@google.com>2020-03-06 14:03:35 +0900
committerJiyong Park <jiyong@google.com>2020-03-10 07:56:29 +0000
commitec829ed4ea3e0b2e1444ee4dfef660c49e392292 (patch)
treee45ad8e3c7736d2e98002b08d7118feccc2a6556 /libc/malloc_debug/malloc_debug.cpp
parentf4e3d42f27adcec3342b7c5928842071b991f5a7 (diff)
Statically link libdl.a to linker
When libbase is built for an APEX, it uses dlsym to reflectively access liblog symbols that are added in R. This is because the APEX where libbasse is packaged into might be running in pre-R devices where the symbols don't exist in liblog.so. This however causes a problem for a static executable in an APEX. Since it is in an APEX, the dlsym is used. But libdl.so which provides dlsym is not available to static executable. Currently, the dynamic linker is the only executable in an APEX that all of its dependencies are statically linked. Fixing the issue by providing fake dlsym by statically linking to libdl.a. Bug: 149569129 Test: m Change-Id: I2e9e45d9876c2d6c878e541715389e6d1ef56996
Diffstat (limited to 'libc/malloc_debug/malloc_debug.cpp')
0 files changed, 0 insertions, 0 deletions