[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151007064830.GL28311@example.net>
Date: Wed, 7 Oct 2015 08:48:30 +0200
From: u-uy74@...ey.se
To: musl@...ts.openwall.com
Subject: Re: musl bug or not, real or not? (Was: Update:
pthread_getattr_np() vs explicit runtime) loader
On Tue, Oct 06, 2015 at 07:36:54AM -0700, Isaac Dunham wrote:
> > > ----------------------------------------------------------------
> > > # cat /proc/sys/kernel/randomize_va_space
> > > 2
> > >
> > > $ /pathtomusllibc.so --library-path /pathtogcc-5libs /pathto/jv-convert --help
> > > Usage: jv-convert [OPTIONS] [INPUTFILE [OUTPUTFILE]]
> > >
> > > # 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?
> It's just that nobody cares about gcj, I think.
A good point, indeed.
> Now that Alpine has moved to GCC 5.2, I've tried it with the distro packages.
> I've installed gcc-java;
> with both randomize_va_space = 0 and 2, specifying an alternate path to the
> default musl dynamic linker in the same way you did does not result in a
> segfault.
> Same goes with a local build of musl, using -Os.
Thanks Isaac, appreciated.
Apparently the breakage is not as simple as it looked in my test here.
> HTH,
It does.
> Isaac
Rune
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
