This makes sense: gdb has not yet been updated to reflect any changes made
since mspgcc4. One of those changes was the semantics of the value stored
in the frame pointer; see
http://www.mail-archive.com/[email protected]/msg09775.html
.
If somebody would file a tracker ticket alo
Akhil Piplani gmail.com> writes:
>
> Hi,
>
> While debugging code built with MSPGCC
> (home/windows/mingw/mspgcc-20110716.zip) on the TI launchpad
> (MSP430G2231), I saw that the addresses for the local variables are
> wrong and GDB always shows their values as 0. Further, the addresses
> of s
Hi,
While debugging code built with MSPGCC
(home/windows/mingw/mspgcc-20110716.zip) on the TI launchpad
(MSP430G2231), I saw that the addresses for the local variables are
wrong and GDB always shows their values as 0. Further, the addresses
of successive local variables are increasing instead of
