User forums > Embedded development
MSP430 linux toolchain with C::B
ywi:
The latest nightly debugger plugin passes command "run" instead of "continue" when the run/continue button is pressed:
--- Code: ---Debugger name and version: GNU gdb (GDB) 7.2
[debug]>>>>>>cb_gdb:
[debug]> set width 0
[debug]>>>>>>cb_gdb:
[debug]> set height 0
[debug]>>>>>>cb_gdb:
[debug]> set breakpoint pending on
[debug]>>>>>>cb_gdb:
[debug]> set print asm-demangle on
[debug]>>>>>>cb_gdb:
[debug]> set unwindonsignal on
[debug]>>>>>>cb_gdb:
[debug]> set print elements 0
[debug]>>>>>>cb_gdb:
[debug]> set disassembly-flavor intel
[debug]No symbol "disassembly" in current context.
[debug]>>>>>>cb_gdb:
[debug]> catch throw
[debug]Function "__cxa_throw" not defined.
[debug]Catchpoint 1 (throw)
[debug]>>>>>>cb_gdb:
[debug]> source /usr/share/codeblocks/scripts/stl-views-1.0.3.gdb
[debug]>>>>>>cb_gdb:
[debug]> directory /projects/test/
[debug]>>>>>>cb_gdb:
[debug]> directory /projects/
[debug]>>>>>>cb_gdb:
[debug]> tty /dev/pts/3
[debug]Queued:[tty /dev/pts/3]
[debug]>>>>>>cb_gdb:
Continuing...
[debug]> run
[debug]Don't know how to run. Try "help target".
[debug]>>>>>>cb_gdb:
Starting the debuggee failed: Don't know how to run. Try "help target".
[debug]> quit
Debugger finished with status 0
--- End code ---
For burning the flash, gdb send specific commands (erase, load, ...) to the debugger proxy, which is himself connected to a programmer.
oBFusCATed:
For the burning: Then you need to put the commands in a file and then use the source command in combination with the 'do not run mode'.
For the run command: I see no remote debugging commands, so I guess you've not set them and you're in native/local debugging mode, thus run is the normal command to use.
ywi:
Yes, I already used successfully a file at gdb start to run particular commands. But still sometimes gdb is launched and reprogramming the flash is not necessary. How to distinguish between both? Usually tools working on remote targets have separate buttons for connect to target and burn.
For your second comment, could you give me some details on where to set "native" and "remote" specific mode parameters?
Thx.
oBFusCATed:
--- Quote from: ywi on May 14, 2012, 11:23:21 pm ---Yes, I already used successfully a file at gdb start to run particular commands. But still sometimes gdb is launched and reprogramming the flash is not necessary. How to distinguish between both? Usually tools working on remote targets have separate buttons for connect to target and burn.
--- End quote ---
Do you see the edit box at the bottom of the debugger's log?
There you can enter commands, so if you're in do-not-run mode you can start gdb then if necessary you can execute the source command manually and then you can start debugging.
Isn't this what you want?
--- Quote from: ywi on May 14, 2012, 11:23:21 pm ---For your second comment, could you give me some details on where to set "native" and "remote" specific mode parameters?
--- End quote ---
I already have shown you - in the project -> properties -> debugger -> remote...
ywi:
OK, I have all information on the configuration possibilities of the debugger. It can partially cover remote debugging needs. As I mentioned, sometimes gdb is launched and reprogramming the flash is not necessary, so a separate toolbar button to burn the flash would be a plus.
Could you help me on the registry window problem? Here is the information printed with command "info registers":
--- Code: ---pc/r0: a702 sp/r1: 2bb0 sr/r2: 001b r3: 0000
fp/r4: ffff r5: 5a0c r6: ffb4 r7: ffff
r8: ffff r9: ffff r10: ffb4 r11: ffff
r12: 0001 r13: 0000 r14: 0340 r15: 0000
--- End code ---
Thanks.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version