From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.0 required=5.0 tests=MAILING_LIST_MULTI,
	RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,RDNS_NONE,
	SPF_PASS autolearn=ham autolearn_force=no version=3.4.2
Received: (qmail 9403 invoked from network); 10 Mar 2020 13:41:28 -0000
Received-SPF:  pass (mother.openwall.net: domain of lists.openwall.com
  designates 195.42.179.200 as permitted sender)
  receiver=inbox.vuxu.org; client-ip=195.42.179.200
  envelope-from=<musl-return-15541-ml=inbox.vuxu.org@lists.openwall.com>
Received: from unknown (HELO mother.openwall.net) (195.42.179.200)
  by inbox.vuxu.org with ESMTP; 10 Mar 2020 13:41:28 -0000
Received: (qmail 32602 invoked by uid 550); 10 Mar 2020 13:41:26 -0000
Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm
Precedence: bulk
List-Post: <mailto:musl@lists.openwall.com>
List-Help: <mailto:musl-help@lists.openwall.com>
List-Unsubscribe: <mailto:musl-unsubscribe@lists.openwall.com>
List-Subscribe: <mailto:musl-subscribe@lists.openwall.com>
List-ID: <musl.lists.openwall.com>
Reply-To: musl@lists.openwall.com
Received: (qmail 32582 invoked from network); 10 Mar 2020 13:41:26 -0000
Date: Tue, 10 Mar 2020 09:41:13 -0400
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Message-ID: <20200310134113.GZ11469@brightrain.aerifal.cx>
References: <CA+689BUjaBOnRqT3COYosNdegs+D11QhgbdB-x31+RqxA+p3bg@mail.gmail.com>
 <20200310095949.GJ14278@port70.net>
 <CA+689BV7Ukgvdgudmz0gxzbEf-ubZ18WztS51zP0x0TvfhYEyw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CA+689BV7Ukgvdgudmz0gxzbEf-ubZ18WztS51zP0x0TvfhYEyw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [musl] musl and jemalloc support

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.

Rich