This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: finding out what's taking space in .bss


On Mon, 2004-02-09 at 07:16, heinricg@esiee.fr wrote:
> >  
> > > I'm looking for advice on how to reduce RAM requirements, which
> > > packages usually take space, how to find out where objects that
> take
> > > space are located.
> > 
> > Starting with the minimal template is probably a good idea. Than add
> > any packages you do need. 
> > 
> >     Andrew
> > 
> 
> as you said, the symbol must have been automatically added by the
> build system. After getting rid of the memalloc package, it
> disappeared.
> After removing many packages, the code size was divided by 4, but the
> .bss section size was just down to about 12k. However, when I use the
> nm command, the biggest object is 0x84 bytes long and I don't get that
> many objects. I guess the sum of the object sizes within .bss is below
> 1KB.
> 
> Is there some kind of buffer or anything that is located in .bss but
> not showed by nm?
> 
> Would you suggest another way of investigating the contents of .bss?

What you see in the map is what you'll use (if you're not using a heap).

Maybe now that you've whittled it down, you could send the map (sort
it using -n) and we can comment.
-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]