Re: ls: can't open '.': Cannot allocate memory
Larry Baker <[email protected]>
| Newsgroups | gmane.linux.uclinux.devel |
|---|---|
| Message-ID | <[email protected]> |
Luis, On 29 Oct 2012, at 12:38 PM, Luis Alves wrote: > Thanks for the explanation Larry. > > Meanwhile I've read some stuff about non-MMU memory alocation (I had > the wrong idea of how memory was allocated). > I guess my system ram is not that much (only 8Mb)... I have the same situation. I have a Lantronix EDS2100 which uses a ColdFire 5208 with 8 MB RAM and 8 MB flash. I was able to obtain more RAM by using the XIP option (enabled by a boot loader command) and by eliminating the RAM tmpfs (I had to edit a uClinux startup file). I do not know if these techniques are possible on your hardware. > How would shared libs solve the problem? All programs would share a single copy of uclibc. Presumably, your applications need it, so it would already be loaded when you run the ls command. I have no idea yet how to do this. > The problem is allocating memory for 'ls' data and not 'ls' itself. Is > this correct? It looks to me like it is coming from the ls command itself, not from the loader. > > Thanks > > Larry Baker US Geological Survey 650-329-5608 [email protected] _______________________________________________ uClinux-dev mailing list [email protected] http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by [email protected] To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev