From: Javier Viguera <javier.viguera@digi.com>
To: buildroot@busybox.net
Subject: [Buildroot] init segfaults when compiled with glibc
Date: Wed, 31 Mar 2010 16:37:09 +0200 [thread overview]
Message-ID: <hovmml$391$1@dough.gmane.org> (raw)
In-Reply-To: <j2i478c82f01003310718gbaf125f7t382a3dd8ac5b3823@mail.gmail.com>
Alexander (Sasha) Sirotkin wrote:
>
> You are right, nevertheless the isssue, i.e. init sudden death is not
> related to the instruction set - as I already mentioned, it works just
> fine with uClibc. The problem appears only when I use external glibc
> based toolchain.
I had the same problem a month ago more or less. With a glibc toolchain
built with crosstool-NG the init process was dying and the kernel
panic'ing as a result because init (pid=1) was not supposed to die.
Unfortunately i could not manage to find what the problem was. All i
found is that it was happening with some versions of glibc while it was
working with other versions: glibc-2.9 was failing, so my workaround was
finally to select EGLIBC-2.10 to build the toolchain. With that version
it worked for me.
Give it a try to a newer version of glibc/eglibc (starting with 2.10)
and let us know if it works.
--
Regards,
Javier Viguera
Software Engineer
Digi International Spain, S.A.
http://www.digi.com
next prev parent reply other threads:[~2010-03-31 14:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 14:26 [Buildroot] init segfaults when compiled with glibc Sasha Sirotkin
2010-03-30 16:58 ` Yann E. MORIN
2010-03-30 22:20 ` Eric BENARD
2010-03-31 14:18 ` Alexander Sirotkin
2010-03-31 14:37 ` Javier Viguera [this message]
2010-03-31 15:48 ` Alexander Sirotkin
2010-03-31 18:11 ` Peter Korsgaard
2010-03-31 18:28 ` Sasha Sirotkin
2010-03-31 18:58 ` H Hartley Sweeten
2010-03-31 19:02 ` Sasha Sirotkin
2010-03-31 19:16 ` Thomas Petazzoni
2010-03-31 20:21 ` Alexander Sirotkin
2010-04-01 7:48 ` Alexander Sirotkin
-- strict thread matches above, loose matches on Subject: below --
2010-03-31 10:47 Sasha Sirotkin
2010-03-31 18:52 ` Thomas Petazzoni
2010-03-31 20:05 ` Alexander Sirotkin
2010-03-30 20:03 Sasha Sirotkin
2010-03-30 20:34 ` Thomas Petazzoni
2010-03-30 12:27 Sasha Sirotkin
2010-03-30 13:20 ` Yann E. MORIN
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='hovmml$391$1@dough.gmane.org' \
--to=javier.viguera@digi.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.