mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Kaisrlík, Jan" <jan.kaisrlik@avast.com>
To: musl@lists.openwall.com
Subject: [musl] musl and jemalloc support
Date: Tue, 10 Mar 2020 10:32:08 +0100	[thread overview]
Message-ID: <CA+689BUjaBOnRqT3COYosNdegs+D11QhgbdB-x31+RqxA+p3bg@mail.gmail.com> (raw)

Hello guys,

I would like to ask about the support of external malloc and jemalloc.
I find an old mail in ML claiming that support is not there and using
external malloc function can potentially cause problems[1] and a
thread[2] on jemalloc saying the same. On the other hand, I find a lot
of pages comparing speed like pages [3] and also I noticed that Musl
claims "replacement of malloc is now allowed/supported" statement in
changelog [4]. So, my expectation is Musl from version 1.1.20 supports
the loading of external malloc function and it is working. Is my
assumption correct? Does it have any limitations, e.g., it has to be
done in compilation time, is LD_PRELOAD supported?

The reason why I'm asking is that some apps started crashing with a
weird coredump from the moment I used
LD_PRELOAD=/usr/lib/libjemalloc.so.2:/usr/lib/libpthread.so.

Thank you for your answer.

The best,
Jan

[1]: https://www.openwall.com/lists/musl/2014/08/08/11
[2]: https://github.com/jemalloc/jemalloc/issues/1443
[3]: https://users.rust-lang.org/t/optimizing-rust-binaries-observation-of-musl-versus-glibc-and-jemalloc-versus-system-alloc/8499/7
[4]: https://git.musl-libc.org/cgit/musl/tree/WHATSNEW#n1916

             reply	other threads:[~2020-03-10  9:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10  9:32 Kaisrlík, Jan [this message]
2020-03-10  9:59 ` Szabolcs Nagy
2020-03-10 11:08   ` Kaisrlík, Jan
2020-03-10 13:41     ` Rich Felker
2020-03-10 14:04       ` Kaisrlík, Jan
2020-03-10 15:47         ` Rich Felker
2020-03-10 19:52           ` Andre McCurdy
2020-03-10 20:17             ` Rich Felker
2020-03-10 23:40               ` Andre McCurdy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+689BUjaBOnRqT3COYosNdegs+D11QhgbdB-x31+RqxA+p3bg@mail.gmail.com \
    --to=jan.kaisrlik@avast.com \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).