Hello, when I run a program via msp430-gdb and stop it with "^c" it is stopped by a reset. That means the PC is overwritten with 0x1100. Thats bad because there is no way to simply backtrace the stack of the program: bt stops after the reset-vector-frame. I cant solve the problem whith break- or watchpoints because the error occurs extremely seldom. The only way is to backtrace the stack whith a stack-memory dump and an asm-listing "by hand" which is very error-prone an slow. There are some other debuggers who provide the correct PC at a "suspend" (thats what "^c" is called in eclipse) but cant read the debug-symbols produced by gcc for easy debugging.
Can you confirm the 'PC=0x1100 at "^c"'-behavior of msp430-gdb or am I doing something wrong? Thanks in advance, Robert
