Hello,
I'm new to mspgcc and am having some problems with the gdb.
'next' commands always seem to take me inside function calls.
I get the same behavior using the msp430-gdbproxy and using
the 'sim' target.
I'm running binaries from mspgcc-20040723.exe from a cygwin
shell on a w2k machine.
The program was compiled with:
$ msp430-gcc -g -o test test.c -mmcu=msp430x169
gdb output follows. The last 'n' command enters the get_status()
function instead of breaking on the next line of main().
Thanks in advance,
Kurt
--- msp430-gdb output ---
$ msp430-gdb test
GNU gdb 6.0
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-cygwin --target=msp430"...
(gdb) set remoteaddresssize 64
(gdb) set remotetimeout 999999
(gdb) target remote localhost:2000
Remote debugging using localhost:2000
0x00001100 in _reset_vector__ ()
(gdb) monitor erase
Erasing target flash - all... Erased OK
(gdb) load test
Loading section .text, size 0x3c2 lma 0x1100
Loading section .data, size 0x4 lma 0x14c2
Loading section .vectors, size 0x20 lma 0xffe0
Start address 0x1100, load size 998
Transfer rate: 1596 bits/sec, 199 bytes/write.
(gdb) b test.c:105
Breakpoint 1 at 0x1398: file test.c, line 105.
(gdb) c
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
main () at test.c:105
105 U0CTL &= ~SWRST;
(gdb) n
107 status = get_status();
(gdb) n
Program received signal SIGTRAP, Trace/breakpoint trap.
get_status () at test.c:22
22 {
(gdb)
