From: Robert Yang <liezhi.yang@windriver.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: "Zhao, Zhenfeng" <Zhenfeng.Zhao@windriver.com>
Subject: glibc detected *** groupadd: malloc(): memory corruption
Date: Mon, 18 Jun 2012 17:17:14 +0800 [thread overview]
Message-ID: <4FDEF21A.5020004@windriver.com> (raw)
Hi Experts:
I've met a strange issue, when set the length of builddir to
266 (Why I did this is that I need to know how long the tmpdir
that oe-core can support):
NOTE: package dbus-1.4.20-r3.0: task do_install: Started
*** glibc detected *** groupadd: malloc(): memory corruption: 0x000000000101da70 ***
*** glibc detected *** groupadd: malloc(): memory corruption: 0x000000000101da70 ***
Then the build would hang, this is caused by the command:
PSEUDO_PREFIX=/too/long/path/tmp/sysroots/x86_64-linux/usr
PSEUDO_LOCALSTATEDIR=... PSEUDO_PASSWD=...
PSEUDO_NOSYMLINKEXP=1 PSEUDO_DISABLED=0 PSEUDO_LOCALSTATEDIR
... /too/long/path/to/tmp/sysroots/x86_64-linux/usr/bin/pseudo
groupadd --root /too/long/path/to/tmp/sysroots/qemux86 -r netdev -f
1) I had looked into the code of groupadd, and found that this would
happen when it used the glibc function which needs malloc(for example,
the access()), so it seemed this was caused by the glibc or pseudo,
but I didn't know why it only happened to groupadd/useradd.
2) I had tried not to use pseudo, it worked well:
sudo groupadd --root /too/long/path/to/tmp/sysroots/qemux86 -r netdev -f
From this, it seemed that the glibc was ok
3) I had tried to write a small piece of code which used the access(), and
used pseudo to run it, it worked well:
/too/long/path/for/pseudo/settings/and/then/run/pseudo my_app
From this, it seemed that both pseudo and glibc were OK.
These 3 steps make me puzzle, maybe we can think that the tmpdir can not
be too long, and limit it to a proper length, please see this:
http://lists.linuxtogo.org/pipermail/openembedded-core/2012-May/022112.html
BTW. the "argument list too long" error has been fixed.
Any suggestion is appreciated.
--
Thanks
Robert
next reply other threads:[~2012-06-18 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 9:17 Robert Yang [this message]
2012-06-18 17:47 ` glibc detected *** groupadd: malloc(): memory corruption Mark Hatle
2012-06-20 6:07 ` Robert Yang
2012-06-21 15:46 ` Saul Wold
2012-06-21 15:57 ` Mark Hatle
2012-06-23 3:09 ` Robert Yang
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=4FDEF21A.5020004@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=Zhenfeng.Zhao@windriver.com \
--cc=openembedded-core@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox