From: Phil Blundell <pb@pbcl.net>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] glibc: Upgrade to 2.25
Date: Fri, 13 Jan 2017 18:45:33 +0000 [thread overview]
Message-ID: <1484333133.3966.76.camel@pbcl.net> (raw)
In-Reply-To: <CAJTo0LZYiqp+b7hwsGaZDKbpwo4UPxyLLw7Eje1-Y5Fg-=Jwow@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
On Wed, 2017-01-11 at 12:19 +0000, Burton, Ross wrote:
> > > The gdk-pixbuf link does use -lpthread, is this saying that libpng
should be linked against pthread too? I can replicate on demand if
you have any suggestions.
>
>
So, amusingly, it now appears that libpng in pthread-using programs has
actually been a bit broken for a long time, since about glibc 2.22.
It's just that the failure has now become more obvious, because ld.so
will refuse to load the binary at all rather than allowing it to load
and having it crash later under some circumstances.
Whether the circumstances that would cause the crash (libpng calling
longjmp) can ever arise with gdk-pixbuf is another question and I don't
know the answer offhand. If this can happen then it would probably be
when dealing with a corrupted input file.
Anyway, this is definitely a glibc bug and it is now on the list of
blockers for 2.25. Good work by Ross in finding it!
p.
[-- Attachment #2: Type: text/html, Size: 1183 bytes --]
next prev parent reply other threads:[~2017-01-13 18:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 3:51 [PATCH 1/2] grub-git: Upgrade to tip of master and fix with glibc 2.25 Khem Raj
2017-01-11 3:51 ` [PATCH 2/2] glibc: Upgrade to 2.25 Khem Raj
2017-01-11 12:19 ` Burton, Ross
2017-01-11 15:56 ` Phil Blundell
2017-01-11 16:21 ` Khem Raj
2017-01-11 16:54 ` Phil Blundell
2017-01-13 18:45 ` Phil Blundell [this message]
2017-01-13 18:52 ` Khem Raj
2017-01-13 20:20 ` Phil Blundell
2017-01-11 15:44 ` Phil Blundell
2017-01-11 15:53 ` Burton, Ross
2017-01-11 16:09 ` Khem Raj
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=1484333133.3966.76.camel@pbcl.net \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox