User forums > Embedded development
Debugging MSP430 from within C::B
cichmen:
Yes, I'm sure. You can see it in the log: "target remote tcp:127.0.0.1:2000".
pfong:
--- Quote from: oBFusCATed on May 07, 2010, 01:09:56 pm ---
--- Quote from: cichmen on May 07, 2010, 10:29:12 am ---Run/Continue in latest nightly build:
When I press Debug / Continue first time, it will not run (see log below). When I press it second time, it works as expected.
--- End quote ---
Are you sure that you've setup the remote debugging info needed by C::B (In the project properties)?
--- End quote ---
I'm running into this same problem using a OpenOCD ARM target. It seems to be related to the "Do *not* run debugee" setting. If the setting is not checked, your program runs to the first break point and things work as expected. If the setting is checked, it stops at the first instruction your program image and the first time you press run/continue it sends "run" to GDB which complains. The second time you press run/continue it sends "continue" and things work as expected.
pfong:
--- Quote from: dmcminn_iwc on April 27, 2010, 03:03:56 pm ---For the use of "run" vs "cont", once the application has started, if you click the "Debug / continue" toolbar button so that it issues the "run" command and then send the "cont" command through the "user debug command" menu item the state of the debugger and UI are synchronised and the toolbar can be used as normal.
--- End quote ---
I've made this bug #017441.
--- Quote from: dmcminn_iwc on April 27, 2010, 03:03:56 pm ---For the use of Ctrl-C to break into a running process I can see that this is not possible due to the use of wxProcess to run the debugger, and wxProcess does not support sending Ctrl-C to child applications directly.
--- End quote ---
I've made this bug #017451. Unfortunately this makes Code::Blocks unusable as an IDE on Windows for embedded development.
oBFusCATed:
Do you know if the problem happens for normal remote debugging (PC <-> PC) ?
I don't have any experience with embedded development and I can test or improve the code.
But if the behaviour is the same when the connection is PC<->PC I can.
pfong:
--- Quote from: oBFusCATed on August 21, 2010, 11:47:53 am ---Do you know if the problem happens for normal remote debugging (PC <-> PC) ?
I don't have any experience with embedded development and I can test or improve the code.
But if the behaviour is the same when the connection is PC<->PC I can.
--- End quote ---
Yes, the run vs cont problem occurs even when the target is a PC. I ran "gdbserver :2314 helloworld" in a terminal window and set the remote target in the project to 127.0.0.1:2314.
Are you also asking if the stop button not working depends on it being a remote target?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version