On Thu, Apr 08, 2010 at 10:50:20AM +0200, Christoph Baumann wrote: > > Hi Cristoph, > > > > have you tried to increase the application stack during compiling phase. > > If you use a gcc-like compiler, you should use the flag -Wl,-elf2flt="-s > > 8192", where 8192 stands for 8KB stack. > > > > In my case, it worked. > > Thanks for this hint. I tried already 128k to no avail.
There is a file in /proc that should show the fragment sizes available. I can't remember the name right now, but it might be /proc/slabinfo. After all if you have 5MB free, but it consists of 80 64kb fragments, then can't allocate 4MB. Of course if you have a single 4MB chunk, it may be that the allocator has to use a little bit of the block for managing it, in which case malloc 4MB would require an 8MB chunk to give 4MB+overhead, while malloc(4MB-4KB) only needs 4MB because the overhead is less than 4KB. I haven't looked at how the memory management in the kernel does any overhead (I thought it was all stored in the first chunk of ram in fixed locations, but there may be libc overhead too that affects things). -- Len Sorensen _______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
