From: u-wsnj@aetey.se
To: musl@lists.openwall.com
Subject: Re: pthread_getattr_np() vs explicit runtime loader
Date: Mon, 21 Sep 2015 09:57:19 +0200 [thread overview]
Message-ID: <20150921075719.GV12087@example.net> (raw)
In-Reply-To: <20150920194132.GO17773@brightrain.aerifal.cx>
On Sun, Sep 20, 2015 at 03:41:32PM -0400, Rich Felker wrote:
> > These _are_ several of the binaries of gcc-5.x which crash. It looks like
> > the ones which crash (java-related ones?) are using pthread_getattr_np()
> > while others do not. I did not though consequently check all of them.
> >
> > You can easily test this if you have got say a jv-convert binary of
> > gcc-5.2.0, dynamically linked with musl and run this binary via the
> > explicit loader. Yours and mine environments are different but I would
> > not be surprised if the binary crashes for you too.
>
> I might get a chance to look later, but first thought: is jv-convert
Unfortunately I could not get any useful backtrace from gdb, this
would need more time.
Hope you would make a simple crash test with
/<path-to-musl>/libc.so /<path-to>/jv-convert.
> using boehm gc? I ask because boehm is one of the main users (iirc) of
Libjava (and then presumably jv-convert too) involves boehm gc.
> pthread_getattr_np and it's full of UB. It's possible that gcc 5 broke
> some of the things it's doing, or that they were already broken but
> didn't happen to crash before. I think boehm needs some patches to
> work safely on musl but maybe not anymore.
boehm needs some patches to be buildable but this is about removing
harmful glibc-related include/define heuristics.
For the record, there are no similar crashes of jv-convert or other
binaries from an older gcc (4.2.3) built with the same musl.
Rune
next prev parent reply other threads:[~2015-09-21 7:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-20 6:39 u-wsnj
2015-09-20 16:34 ` Rich Felker
2015-09-20 17:22 ` u-wsnj
2015-09-20 18:27 ` Rich Felker
2015-09-20 19:30 ` u-wsnj
2015-09-20 19:41 ` Rich Felker
2015-09-21 7:57 ` u-wsnj [this message]
2015-09-30 15:43 ` u-uy74
2015-09-30 20:35 ` Update: [musl] " u-uy74
2015-10-06 11:34 ` musl bug or not, real or not? (Was: [musl] Update: [musl] pthread_getattr_np() vs explicit runtime) loader u-uy74
2015-10-06 14:36 ` Isaac Dunham
2015-10-07 6:48 ` u-uy74
2015-10-06 17:07 ` Rich Felker
2015-10-07 7:27 ` u-uy74
2015-10-07 7:43 ` Timo Teras
2015-10-07 10:59 ` u-uy74
2015-10-08 16:48 ` Rich Felker
2015-10-09 5:39 ` Timo Teras
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=20150921075719.GV12087@example.net \
--to=u-wsnj@aetey.se \
--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).