From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: AVR32 segfaults / Disablng virtual/libintl?
Date: Fri, 16 May 2008 23:24:54 +0200 [thread overview]
Message-ID: <g0ku37$m4g$1@ger.gmane.org> (raw)
In-Reply-To: <200805161611.50480.geoffrey@pager.net>
Geoffrey Wossum wrote:
> Hi all,
>
> I've had some odd segfaults on my AVR32 system, mostly involving avahi (always
> on startup) and the occasional Xfbdev crash. I didn't bother looking into it
> until now, because aplay was always crashing before it even got to main(),
> which was making difficult to test my sound CODEC.
>
> I found that both avahi-daemon and aplay were both crashing before they got to
> main(), and they both crashed due to infinite recursion calling the function
> _pthread_cleanup_push_defer().
>
> Due to the crash being in a thread related function, I focused my initial
> attention there, but now I think the problem is related to gettext. If I
> hand compile aplay and keep it from linking against libintl, it doesn't
> crash. Haven't tried the same thing on avahi, but I suspect libintl/gettext
> is also the problem there since they were crashing exactly the same way.
>
> I don't need any i18n any these types of applications. As a workaround, can I
> keep gettext from being built and use the libintl stubs provided by uClibc?
> How do I do this? PREFERRED_PROVIDER_virtual/libintl = ""?
> PREFERRED_PROVIDER_virtual/libintl = "uclibc"?
That should work as long as you have wchar and intl stubs in uclibc. I
would *very* much like to use the uclibc ones instead of the gettext
ones, if only to get cleaner builds :)
regards,
Koen
>
> TIA,
> ---
> Geoffrey
next prev parent reply other threads:[~2008-05-16 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 21:11 AVR32 segfaults / Disablng virtual/libintl? Geoffrey Wossum
2008-05-16 21:24 ` Koen Kooi [this message]
2008-05-19 14:07 ` Geoffrey Wossum
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='g0ku37$m4g$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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 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.