Re: Size of global variable

On Mon, Jul 29, 2013 at 6:06 PM, Daniel Beer <[email protected]> wrote:

> On Mon, Jul 29, 2013 at 05:50:39PM -0500, Peter Bigot wrote:
> > The extra word is probably the watchdog timer clear value, which is
> > initialized on reset.  You can exclude it by using -mdisable-watchdog.
> > mspgcc uses different sections than AVR, and for mspgcc .noinit is not
> > merged with .bss.  With the default linker script .noinit is between the
> > bottom of the stack and the top of .bss.
> >
> > You can use msp430-objdump -x app.elf to see the list of sections
> available
> > and what's in them (at what address).  That information can tell you
> what's
> > going to be below the stack, hence the first thing that would get
> > overwritten when it overruns.
>
> Hrmm, so it appears then that when "size" says "bss" it actually means
> the sum of sections which are marked ALLOC but not LOAD, rather than
> literally the .bss section. Is that correct?
>

Maybe.  I have one program where the length of the .bss section is 2222
bytes and the length of the .noinit section is 2 bytes, and msp430-size
says it has 2224 bytes in bss.  I couldn't say what else might go into
size's conception of bss length if some of the more esoteric features of
the linker script are exercised.

Peter

------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk

_______________________________________________
Mspgcc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users