mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [musl] musl and jemalloc support
Date: Tue, 10 Mar 2020 11:47:54 -0400	[thread overview]
Message-ID: <20200310154754.GA11469@brightrain.aerifal.cx> (raw)
In-Reply-To: <CA+689BVJ-oPJME=bo4r8Mc2PsSQPd+1axiLsD9nn_h2Pz8mYLg@mail.gmail.com>

On Tue, Mar 10, 2020 at 03:04:48PM +0100, Kaisrlík, Jan wrote:
> On Tue, Mar 10, 2020 at 2:41 PM Rich Felker <dalias@libc.org> wrote:
> >
> > On Tue, Mar 10, 2020 at 12:08:57PM +0100, Kaisrlík, Jan wrote:
> > > > the fact that you have libpthread.so means it's not a musl system
> > > > and preloading a libpthread.so from another libc is expected to
> > > > crash. (even on other systems you should not just preload libpthread,
> > > > but libjemalloc should have it in its dependencies if needed.)
> > > >
> > >
> > > Sorry, I kept libpthread from one of my previous tests which is slightly
> > > misleading in this case. My system has only one libpthread library coming
> > > from musl.
> >
> > musl has no libpthread.so, only libpthread.a (which is empty). If you
> > have a libpthread.so, something probably went badly wrong in setting
> > up your system.
> 
> Thank you for pointing this. Fortunately, it is symlink to libc.
> 
> ls -la usr/lib/libpthread.so
> lrwxrwxrwx 1 X X 7 Mar  5 15:02 usr/lib/libpthread.so -> libc.so

That's still wrong. Recent musl will go out of its way to prevent you
from shooting yourself in the foot like that, but older musl will blow
up horribly. In either case the file should not exist.

Rich

  reply	other threads:[~2020-03-10 15:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10  9:32 Kaisrlík, Jan
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 [this message]
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=20200310154754.GA11469@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --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).