From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/8624 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: musl bug or not, real or not? (Was: [musl] Update: [musl] pthread_getattr_np() vs explicit runtime) loader Date: Tue, 6 Oct 2015 13:07:55 -0400 Message-ID: <20151006170755.GQ8645@brightrain.aerifal.cx> References: <20150920063909.GO12087@example.net> <20150920163405.GK17773@brightrain.aerifal.cx> <20150920172237.GR12087@example.net> <20150920182728.GM17773@brightrain.aerifal.cx> <20150920193033.GS12087@example.net> <20150920194132.GO17773@brightrain.aerifal.cx> <20150930154337.GC13149@example.net> <20150930203548.GF13149@example.net> <20151006113451.GI28311@example.net> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1444151293 8151 80.91.229.3 (6 Oct 2015 17:08:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 6 Oct 2015 17:08:13 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-8636-gllmg-musl=m.gmane.org@lists.openwall.com Tue Oct 06 19:08:11 2015 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1ZjVik-0000tJ-Qu for gllmg-musl@m.gmane.org; Tue, 06 Oct 2015 19:08:10 +0200 Original-Received: (qmail 9277 invoked by uid 550); 6 Oct 2015 17:08:08 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 9259 invoked from network); 6 Oct 2015 17:08:08 -0000 Content-Disposition: inline In-Reply-To: <20151006113451.GI28311@example.net> User-Agent: Mutt/1.5.21 (2010-09-15) Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:8624 Archived-At: On Tue, Oct 06, 2015 at 01:34:51PM +0200, u-uy74@aetey.se wrote: > Either nobody cares or nobody has a gcc-5.x toolchain built with musl? > Wondering. > > gcc-5 looks like a case important enough to care. It's not that I'm uninterested, just that there does not yet seem to be any reason to believe it's a bug in musl or any easy test-case to reproduce the problem, so I wouldn't even know where to get started... I think you really need to find a way to use what debugging tools you have to figure out what's going on and where the actual source of the crash is. Rich > On Wed, Sep 30, 2015 at 10:35:48PM +0200, u-uy74@aetey.se wrote: > > On Wed, Sep 30, 2015 at 05:43:37PM +0200, u-uy74@aetey.se wrote: > > > > > > I still think that the crashes are caused by errors > > > while guessing the stack placement in pthread_getattr_np(), > > > simply because of the kernel doing something else than usual. > > > > I can reproduce the problem and this looks like something > > to fix or at least work around, either in gcc or in musl. > > > > Running with the implicit loader works, but using the explicit one yields: > > > > ---------------------------------------------------------------- > > # cat /proc/sys/kernel/randomize_va_space > > 2 > > > > $ /pathtomusllibc.so --library-path /pathtogcc-5libs /pathto/jv-convert --help > > Usage: jv-convert [OPTIONS] [INPUTFILE [OUTPUTFILE]] > > > > Convert from one encoding to another. > > > > --encoding FROM > > --from FROM use FROM as source encoding name > > --to TO use TO as target encoding name > > -i FILE read from FILE > > -o FILE print output to FILE > > --reverse swap FROM and TO encodings > > --help print this help, then exit > > --version print version number, then exit > > > > `-' as a file name argument can be used to refer to stdin or stdout. > > > > # echo 0 > /proc/sys/kernel/randomize_va_space > > > > $ /pathtomusllibc.so --library-path /pathtogcc-5libs /pathto/jv-convert --help > > Segmentation fault > > ---------------------------------------------------------------- > > > > Would anybody try this and confirm or refute? > > > > Rune