From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] e2fsck crashes
Date: Thu, 23 Sep 2010 22:26:46 +0200 [thread overview]
Message-ID: <878w2s8aux.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4C9B3DBC.7040700@signaturealpha.com> (Marc Leclerc's message of "Thu, 23 Sep 2010 07:45:00 -0400")
>>>>> "Marc" == Marc Leclerc <marc-leclerc@signaturealpha.com> writes:
Marc> Hi,
Marc> Every attemps to include e2fsprogs on my target results in the
Marc> utilities crashing with a segfault.
Marc> Sep 23 01:39:39 sa_linux user.info kernel: e2fsck[987]: segfault at 20
Marc> ip b77316b8 sp bf968534 error 4
Marc> Sep 23 01:39:39 sa_linux user.info kernel: in
Marc> libuClibc-0.9.31.so[b7727000+43000]
Marc> Any idea why
Please provide a bit more details. What buildroot .config are you using
and what is the exact command line that causes a crash?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-09-23 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 11:45 [Buildroot] e2fsck crashes Marc Leclerc
2010-09-23 18:19 ` Thomas Petazzoni
2010-09-23 20:26 ` Peter Korsgaard [this message]
2010-09-24 11:20 ` Marc Leclerc
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=878w2s8aux.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox