jemalloc doesn't look linked

[ltagliamonte-dd]

Hello Friend,
I'm trying to validate that my kvrocks and rocksdb are using jemalloc.
when I try to verify if it is statically linked i don't see anything:

docker run -it --entrypoint=/bin/bash apache/kvrocks:2.10.0
kvrocks@6bd566e45026:/$ which kvrocks
/usr/bin/kvrocks
kvrocks@6bd566e45026:/$ ldd /usr/bin/kvrocks
	linux-vdso.so.1 (0x0000ffff8636d000)
	libssl.so.3 => /lib/aarch64-linux-gnu/libssl.so.3 (0x0000ffff85140000)
	libcrypto.so.3 => /lib/aarch64-linux-gnu/libcrypto.so.3 (0x0000ffff84c00000)
	libm.so.6 => /lib/aarch64-linux-gnu/libm.so.6 (0x0000ffff850a0000)
	libc.so.6 => /lib/aarch64-linux-gnu/libc.so.6 (0x0000ffff84a50000)
	/lib/ld-linux-aarch64.so.1 (0x0000ffff86330000)

i don't see LD_PRELOAD specified:

kvrocks@6bd566e45026:/$ env | grep LD_PRELOAD
kvrocks@6bd566e45026:/$ 

I tried to build kvrocks myself with:

RUN DEBIAN_FRONTEND=noninteractive && apt-get update && apt-get upgrade -y && apt-get -y --no-install-recommends install git build-essential autoconf cmake libtool python3 libssl-dev && apt-get autoremove && apt-get clean

ARG INSTALL_DIR=/opt/kvrocks
ARG KVROCKS_VERSION=v2.10.0
ARG CMAKE_PARALLEL=6
RUN git clone --depth 1 -b ${KVROCKS_VERSION} https://github.com/apache/kvrocks.git ${INSTALL_DIR}
WORKDIR ${INSTALL_DIR}
RUN ./x.py build -DENABLE_OPENSSL=ON -DPORTABLE=1 -DCMAKE_BUILD_TYPE=Release -j ${CMAKE_PARALLEL}

I see it successfully build jemalloc:

config.status: creating Makefile
config.status: creating jemalloc.pc
config.status: creating doc/html.xsl
config.status: creating doc/manpages.xsl
config.status: creating doc/jemalloc.xml
config.status: creating include/jemalloc/jemalloc_macros.h
config.status: creating include/jemalloc/jemalloc_protos.h
config.status: creating include/jemalloc/jemalloc_typedefs.h
config.status: creating include/jemalloc/internal/jemalloc_preamble.h
config.status: creating test/test.sh
config.status: creating test/include/test/jemalloc_test.h
config.status: creating config.stamp
config.status: creating bin/jemalloc-config
config.status: creating bin/jemalloc.sh
config.status: creating bin/jeprof
config.status: creating include/jemalloc/jemalloc_defs.h
config.status: creating include/jemalloc/internal/jemalloc_internal_defs.h
config.status: creating test/include/test/jemalloc_test_defs.h
config.status: executing include/jemalloc/internal/public_symbols.txt commands
config.status: executing include/jemalloc/internal/private_symbols.awk commands
config.status: executing include/jemalloc/internal/private_symbols_jet.awk commands
config.status: executing include/jemalloc/internal/public_namespace.h commands
config.status: executing include/jemalloc/internal/public_unnamespace.h commands
config.status: executing include/jemalloc/jemalloc_protos_jet.h commands
config.status: executing include/jemalloc/jemalloc_rename.h commands
config.status: executing include/jemalloc/jemalloc_mangle.h commands
config.status: executing include/jemalloc/jemalloc_mangle_jet.h commands
config.status: executing include/jemalloc/jemalloc.h commands
===============================================================================
jemalloc version   : 0.0.0-0-g000000missing_version_try_git_fetch_tags
library revision   : 2

CONFIG             : CC= -C --enable-autogen --disable-shared --disable-libdl --with-jemalloc-prefix="" CXX=/usr/bin/c++
CC                 : gcc
CONFIGURE_CFLAGS   : -std=gnu11 -Wall -Wextra -Wsign-compare -Wundef -Wno-format-zero-length -Wpointer-arith -Wno-missing-braces -Wno-missing-field-initializers -Wno-missing-attributes -pipe -g3 -fvisibility=hidden -Wimplicit-fallthrough -O3 -funroll-loops
SPECIFIED_CFLAGS   : 
EXTRA_CFLAGS       : 
CPPFLAGS           : -D_GNU_SOURCE -D_REENTRANT
CXX                : /usr/bin/c++ -std=c++17
CONFIGURE_CXXFLAGS : -Wall -Wextra -g3 -fvisibility=hidden -Wimplicit-fallthrough -O3
SPECIFIED_CXXFLAGS : 
EXTRA_CXXFLAGS     : 
LDFLAGS            : 
EXTRA_LDFLAGS      : 
DSO_LDFLAGS        : -shared -Wl,-soname,$(@F)
LIBS               : -lm -lstdc++ -pthread
RPATH_EXTRA        : 

XSLTPROC           : false
XSLROOT            : 

PREFIX             : /usr/local
BINDIR             : /usr/local/bin
DATADIR            : /usr/local/share
INCLUDEDIR         : /usr/local/include
LIBDIR             : /usr/local/lib
MANDIR             : /usr/local/share/man

srcroot            : /tmp/kvrocks/build/_deps/jemalloc-src/
abs_srcroot        : /tmp/kvrocks/build/_deps/jemalloc-src/
objroot            : 
abs_objroot        : /tmp/kvrocks/build/_deps/jemalloc-build/

JEMALLOC_PREFIX    : ""
JEMALLOC_PRIVATE_NAMESPACE
                   : je_
install_suffix     : 
malloc_conf        : 
documentation      : 1
shared libs        : 0
static libs        : 1
autogen            : 1
debug              : 0
stats              : 1
experimental_smallocx : 0
prof               : 0
prof-libunwind     : 0
prof-libgcc        : 0
prof-gcc           : 0
fill               : 1
utrace             : 0
xmalloc            : 0
log                : 0
lazy_lock          : 0
cache-oblivious    : 1
cxx                : 1
....

What am I missing? is this a bug?

[git-hulk]

@ltagliamonte-dd Kvrocks will static link the jemalloc library while building, so you cannot find it in the shared library.

[ltagliamonte-dd]

thanks i can confirm by looking at objdump:

objdump -t /usr/bin/kvrocks | grep je_m
0000000000965a00 l     F .text	000000000000020c              je_malloc_strtoumax
0000000000923b10 l     F .text	0000000000000ddc              je_malloc_default
0000000000976eb0 l     F .text	00000000000000c0              je_malloc_tsd_boot1
0000000000965f14 l     F .text	0000000000000010              je_malloc_mutex_postfork_parent
0000000000965c10 l     F .text	0000000000000198              je_malloc_mutex_lock_slow
00000000000a29cc l     F .text	0000000000000078              je_malloc_printf
0000000000965db0 l     F .text	000000000000004c              je_malloc_mutex_prof_data_reset
00000000000a28ec l     F .text	0000000000000078              je_malloc_vcprintf
0000000000965964 l     F .text	0000000000000044              je_malloc_write
00000000000a18c4 l     F .text	0000000000000fc0              je_malloc_vsnprintf
0000000000976e24 l     F .text	000000000000008c              je_malloc_tsd_boot0
0000000000965e00 l     F .text	00000000000000b0              je_malloc_mutex_init
0000000000965eb0 l     F .text	0000000000000064              je_malloc_mutex_prefork
0000000000965ff0 l     F .text	0000000000000008              je_malloc_mutex_boot
0000000000965f24 l     F .text	00000000000000c4              je_malloc_mutex_postfork_child
00000000000a2884 l     F .text	0000000000000068              je_malloc_snprintf
0000000000e3190c g     O .data	0000000000000001              .hidden je_malloc_slow
0000000000e82864 g     O .bss	0000000000000004              .hidden je_manual_arena_base
0000000000e319a0 g     O .data	0000000000000018              .hidden je_metadata_thp_mode_names
000000000108ac28 g     O .bss	0000000000000008              .hidden je_max_background_threads
0000000000e31908 g     O .data	0000000000000004              .hidden je_malloc_init_state
0000000000976e10 g     F .text	000000000000000c              .hidden je_malloc_tsd_malloc
0000000000976e20 g     F .text	0000000000000004              .hidden je_malloc_tsd_dalloc
00000000000a2964 g     F .text	0000000000000068              .hidden je_malloc_cprintf

[torwig]

@ltagliamonte-dd

The ldd command only shows dynamic libraries, not static ones. Here's why:

• Dynamic Libraries (shared libraries): These are linked at runtime. When you run a program, the dynamic linker/loader (ld-linux.so) loads the required shared libraries into memory. The ldd command shows you this runtime linking information by listing the dynamic libraries a program depends on.

• Static Libraries: These are linked at compile time and are part of the final executable binary. Static libraries (usually .a files) are not loaded at runtime but are embedded directly into the executable. Since static libraries are incorporated into the program during the build process, there is no need for the program to reference them at runtime, so ldd doesn't show them.

If you're trying to inspect the presence of statically linked libraries, tools like nm, objdump, or readelf are more appropriate, as they allow you to inspect the symbols and sections within the binary.