From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [BUG] eglibc and Kodi Krypton
Date: Wed, 24 Aug 2016 15:10:32 +0200 [thread overview]
Message-ID: <20160824151032.53124166@free-electrons.com> (raw)
In-Reply-To: <npjure$ucu$1@blaine.gmane.org>
Hello,
On Wed, 24 Aug 2016 13:02:07 +0200, Stanislav Vlasic wrote:
> Kodi Krypton causes random crashes when using eglibc (2.18 or 2.19,
> doesnt matter - from 2016.05).
>
> GDB output:
> (gdb) kodi.bin: pthread_mutex_lock.c:347: __pthread_mutex_lock_full:
> Assertion `(-(e)) != 35 || (kind != PTHREAD_MUTEX_ERRORCHECK_NP && kind
> != PTHREAD_MUTEX_RECURSIVE_NP)' failed.
>
> I rebuilt with glibc 2.23 which fixed issue. Platform is aarch64, custom
> 3.14 kernel (Amlogic), not sure if same happens with armel and armhf
> (did not test it).
We no longer support eglibc in Buildroot, and therefore only support
glibc 2.22 and 2.23 in the upcoming 2016.08 release, and 2.22/2.23/2.24
in the next 2016.11 release.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-24 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 11:02 [Buildroot] [BUG] eglibc and Kodi Krypton Stanislav Vlasic
2016-08-24 13:10 ` Thomas Petazzoni [this message]
2016-08-24 16:11 ` Stanislav Vlasic
2016-08-24 16:14 ` Stanislav Vlasic
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=20160824151032.53124166@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.