From: "Koch, Alexander" <akoch@init-ka.de>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] genimage segfaults with glibc 2.22
Date: Tue, 25 Aug 2015 13:41:42 +0200 [thread overview]
Message-ID: <334319B2EBE0B144BAE1402B79D82DC503959F3938@srvpegasus> (raw)
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?
Best regards,
Alex
On Sun, Aug 23, 2015 at 16:46:51 GMT, Clemens Gruber wrote:
> On Sat, Aug 22, 2015 at 08:43:18PM +0200, Alexander Aring wrote:
>> Hi,
>>
>> I currently see an issue with genimage and glibc 2.22. In this version
>> setenv segfaults if setenv (..., NULL, ...).
>>
>> I think glibc fixed again with [0] and there are a couple of mailinglist
>> fights how to deal correctly with "setenv (..., NULL, ...)". [1]
>>
>> Anyway I just want to leave a note here before other people run into the
>> same issue and debug hours "why" genimage segfaults.
>>
>> Maybe genimage should be updated to don't call setenv if value == NULL.
>>
>> - Alex
>>
>> [0] https://sourceware.org/git/?p=glibc.git;a=commit;h=03c1e456b079929a8290ae
b4aadb05c0df73bfd2
>> [1] https://sourceware.org/ml/libc-alpha/2015-03/msg00449.html
>>
>
> Hi,
>
> I was trying to debug that error last week on ArchLinux, thanks for posting
> this
> here!
>
> Regards,
> Clemens
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2015-08-25 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 11:41 Koch, Alexander [this message]
2015-08-25 12:09 ` Alexander Aring
2015-08-25 12:42 ` Alexander Aring
-- strict thread matches above, loose matches on Subject: below --
2015-08-22 18:43 Alexander Aring
2015-08-23 16:46 ` Clemens Gruber
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=334319B2EBE0B144BAE1402B79D82DC503959F3938@srvpegasus \
--to=akoch@init-ka.de \
--cc=ptxdist@pengutronix.de \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox