Re: [ptxdist] genimage segfaults with glibc 2.22

[Alexander Aring <alex.aring@gmail.com>]

On Tue, Aug 25, 2015 at 02:09:15PM +0200, Alexander Aring wrote:
> On Tue, Aug 25, 2015 at 01:41:42PM +0200, Koch, Alexander wrote:
> > Hi,
> > 
> > I stumbled upon this as well, when upgrading glibc under Arch.
> > 
> > So to clarify, do we just need to wait until the patch mentioned by Alex in [0]
> > gets included in an updated glibc package, or is there a proper way to make
> > PTXdist (or better `genimage`) work again under Arch?
> > 
> > 
> 
> No, glibc will always segfault if setenv (..., NULL, ...) since glibc
> 2.22. So far I understand this is because setenv (..., NULL, ...) is
> not defined [0].
> 
> Before glibc 2.22 they handled like VAR="", but this differs when you
> not using glibc. Like uclibc will do a complete different handling
> then (don't know the handling on uclibc, but it's a undef behaviour in
> all libc implementations).
> 
> They also don't decide to return an errno value, because it's not
> defined at [0], so they introduced a core dump.
> 
> This need to be fixed in genimage, I recently send a patch for adding a
> workaround for that [1]. Simple don't call setenv when value is NULL.
> 
> 
> _IMPORTANT NOTE_
> 
> Don't calling setenv != setenv(..., "", ...), I think this differs, the
> different is getenv will return NULL, if name isn't found and if ""
> then getenv return "".
> 

I currently see issues with the workaround solution [1]. Please adapt
the changes which I suggest inside the reply.

- Alex

[1] http://article.gmane.org/gmane.comp.embedded.ptxdist.devel/13240

-- 
ptxdist mailing list
ptxdist@pengutronix.de