[OE-core] glibc detected *** groupadd: malloc(): memory corruption

Mark Hatle mark.hatle at windriver.com
Mon Jun 18 17:47:40 UTC 2012


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.
>





More information about the Openembedded-core mailing list