From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: glibc detected *** groupadd: malloc(): memory corruption
Date: Wed, 20 Jun 2012 14:07:57 +0800 [thread overview]
Message-ID: <4FE168BD.9000906@windriver.com> (raw)
In-Reply-To: <4FDF69BC.6080808@windriver.com>
Thanks Mark, the rpm.real also has the same problem when the length of tmpdir
is 210, it seems that this is because of the glibc.
And also other problems found:
When use PACKAGE_CLASSES = "package_deb", and the length of tmpdir is 177,
the error is:
/too/long/path/totmp/sysroots/x86_64-linux/usr/bin/dpkg-scanpackages: bad
interpreter: No such file or directory
The interpreter is perl, and it does exist, it seems that we should limit
the length of tmpdir to a smaller value then 177 rather than fix these strange
problems. I will go on working on it.
// Robert
On 06/19/2012 01:47 AM, Mark Hatle wrote:
> We're not away of any size limitations within pseudo, other then PATH_MAX which
> is typically 4096...
>
> --Mark
>
> On 6/18/12 4:17 AM, Robert Yang wrote:
>>
>> 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.
>>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
next prev parent reply other threads:[~2012-06-20 6:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 9:17 glibc detected *** groupadd: malloc(): memory corruption Robert Yang
2012-06-18 17:47 ` Mark Hatle
2012-06-20 6:07 ` Robert Yang [this message]
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=4FE168BD.9000906@windriver.com \
--to=liezhi.yang@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