Re: musl bug or not, real or not? (Was: [musl] Update: [musl] pthread_getattr_np() vs explicit runtime) loader

[Rich Felker <dalias@libc.org>]

On Wed, Oct 07, 2015 at 10:43:39AM +0300, Timo Teras wrote:
> On Wed, 7 Oct 2015 09:27:54 +0200
> u-uy74@aetey.se wrote:
> 
> > > 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.  
> > 
> > Pretty remarkably, neither my usual gdb nor Debian's current gdb were
> > able to make sence of the crashes. Probably the thread states became
> > messed up too badly.
> > 
> > Fortunately I do not think any longer that musl is the culprit, nor do
> > I actually need gcj, otherwise have a workaround. Will not pursue this
> > issue further.
> > 
> > Thanks for your feedback, sorry for the noise.
> 
> gcj uses boehm-gc. Alpine has patches for gcc boehm-gc. We are also
> patching gcc's gcj. You can see our full patch set at:
> http://git.alpinelinux.org/cgit/aports/tree/main/gcc
> 
> Some of these may or may not fix the issue you have at had. Not sure
> how your gcc/gcj is built.

Thank you very much for finding the cause of this. Do you know if
these patches have been submitted upstream to gcc and/or boehm?
Obviously assuming by default that __environ is the start of .data and
only doing a proper search on glibc is broken basically everywhere but
glibc. The dl_iterate_phdr stuff should probably use a configure
check; I think one already exists in gcc but the boehm-gc dir might
need its own.

Rich