User forums > Embedded development
Debugging MSP430 from within C::B
oBFusCATed:
--- Quote from: pfong on September 01, 2010, 02:28:56 am ---I've attached a simple helloworld project. I am testing with Code::Blocks 10.05 on Windows. This is the behavior that I observe...
Situation 1:
Make sure "Do *not* run debugee" is checked off (enabled). In one window in the helloworld directory run "gdbserver :1234 bin\Debug\helloworld.exe". In Code::Blocks press the "run/continue" button. You will see the gdbserver report "Remote debugging from host 127.0.0.1". If you press "run/continue" again, it will send "run" to gdb. This causes the gdbserver say "Killing inferior" and exit. The local gdb runs the process locally and a console window pops up.
Situation 2:
Make sure "Do *not* run debugee" is NOT checked off (enabled). In one window in the helloworld directory run "gdbserver :1234 bin\Debug\helloworld.exe". In Code::Blocks press the "run/continue" button. You will see the gdbserver report "Remote debugging from host 127.0.0.1". Then "Hello world!" is printed out in the window with gdbserver and it waits in the while (1) loop.
The behavior in situation 1 is broken. It should send "continue" when you press the "run/continue" so that the process runs where gdbserver is running just like in situation 2.
--- End quote ---
Thanks will test tonight...
--- Quote from: oBFusCATed on August 29, 2010, 09:18:04 pm ---The stop but happens for me too...
--- End quote ---
"but" should have been "bug", sorry for the typo.
And yes, the bug is present on my machine.
And also it will be very hard to solve, probably impossible
or at least will require replacing wxProcess with something else (or patching wxProcess).
I'm still testing and do not have a final opinion on the matter.
oBFusCATed:
The "run/continue" bug should be fixed with this patch: http://forums.codeblocks.org/index.php/topic,10908.msg88984.html#msg88984
oBFusCATed:
The interrupting bug should be fixed with this patch: http://forums.codeblocks.org/index.php/topic,10908.msg89081.html#msg89081
pfong:
Nice work. I have not had time to try a build of the debugger branch yet though. I've been using Code::Blocks on Ubuntu instead.
Should we update the bugs in the bug tracker 017441 and 017451? I'm not familiar with the Berilos bug tracker and don't see how to update the status.
BTW, has any one working on the debugger branch looked at bug 017461 ""Additional GDB Commands -> Before Connection" broken"? I discovered that problem while trying to setup the target board using GDB commands in that setting. The bug report was submitted by my colleague.
oBFusCATed:
--- Quote from: pfong on September 09, 2010, 11:31:14 pm ---Should we update the bugs in the bug tracker 017441 and 017451? I'm not familiar with the Berilos bug tracker and don't see how to update the status.
--- End quote ---
I think only the devs/admins can do that (also there are some duplicates).
But first verify that the bugs are fixed in your environment....
--- Quote from: pfong on September 09, 2010, 11:31:14 pm ---BTW, has any one working on the debugger branch looked at bug 017461 ""Additional GDB Commands -> Before Connection" broken"? I discovered that problem while trying to setup the target board using GDB commands in that setting. The bug report was submitted by my colleague.
--- End quote ---
I've not, but will look at it some day:)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version