At Tue, 6 Mar 2012 18:51:26 -0800, wayne roberts wrote: > (gdb) bt > #0 0x00000000 in ?? () > #1 0x0000c0c0 in blah,blah..etc.. > (gdb) monitor reset > (gdb) n > Cannot find bounds of current function > (gdb) > > So, when i issue monitor reset, should the program counter and stack > pointer be restored to initial values, then again see _reset_vector__ () at > ../../../gcc-4.6.1/gcc/config/msp430/crt0.S:105 > ??
Hi Wayne, The problem is that gdb isn't aware of any state changes due to "monitor" commands. The state of all registers is sent to GDB every time the program stops, so if you hit a breakpoint or press Ctrl+C, you'll have correct state information. However, when you issue "monitor reset", the chip does get reset, but gdb keeps the state it had before issuing the command. If you try "continue", the state will be correct when the program stops again. Cheers, Daniel -- D.L. Beer Engineering www.dlbeer.co.nz ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
