Date: Mon, 3 Jul 2023 15:21:24 +0000
From: Taylor R Campbell <campbell+netbsd-tech-userle...@mumble.net>
Message-ID: <20230703152125.8798060...@jupiter.mumble.net>
| Not sure why calling malloc or realloc still causes jemalloc.o to be
| pulled in, in the presence of -lbsdmalloc.
libbsdmalloc doesn't appear to provide any of the _malloc_xxx symbols
that jemalloc makes available globally.
_malloc_options (a const char *) is one possibility that something might
be referring to, but it is more likely the
_malloc_prefork() _malloc_postfork() _malloc_postfork_child()
functions which (according to the comments) other code in libc will call
(for threaded programs). If the program isn't threaded, they won't actually
get called, but they're probably still being referenced.
kre
