From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>, "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
OpenEmbedded Devel List
<openembedded-devel@lists.openembedded.org>,
Yocto Discussion Mailing List <yocto@yoctoproject.org>
Subject: Re: [RFT] binutils 2.27
Date: Tue, 09 Aug 2016 16:24:15 +0100 [thread overview]
Message-ID: <1470756255.8166.51.camel@linuxfoundation.org> (raw)
In-Reply-To: <DC67B803-475F-4992-8DFD-B8F5FA7B1D15@gmail.com>
On Tue, 2016-08-09 at 07:42 -0700, Khem Raj wrote:
> I could also see it on ppc. backtrace, shows the segfault is in exit
> path and happens in libc
> at this point, I think the problem is how libc is compiled with
> binutils 2.27, connman itself
> is ok.
Its the issue here:
https://sourceware.org/ml/glibc-bugs/2015-01/msg00274.html
https://sourceware.org/bugzilla/show_bug.cgi?id=17908
Basically, if you remove the global _IO_stdin_used symbol, it triggers
compatibility code which crashes.
I've confirmed that if I add that symbol to the version-script in
connman, things work again.
Any idea how we raise the priority of this issue. There are no comments
on the bug despite it having been posted a while ago :(.
Cheers,
Richard
next prev parent reply other threads:[~2016-08-09 15:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-07 8:39 [RFT] binutils 2.27 Khem Raj
2016-08-08 6:28 ` Richard Purdie
2016-08-08 7:24 ` Khem Raj
2016-08-08 8:14 ` Richard Purdie
2016-08-08 8:50 ` Richard Purdie
2016-08-08 9:16 ` André Draszik
2016-08-08 15:21 ` Khem Raj
2016-08-08 15:59 ` Richard Purdie
2016-08-08 23:16 ` Burton, Ross
2016-08-09 14:42 ` Khem Raj
2016-08-09 15:24 ` Richard Purdie [this message]
2016-08-10 15:25 ` [oe] " Martin Jansa
2016-08-08 23:06 ` 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=1470756255.8166.51.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=ross.burton@intel.com \
--cc=yocto@yoctoproject.org \
/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