User forums > Embedded development
Debugging MSP430 from within C::B
oBFusCATed:
I think, I've gathered enough info, just need to do some testing + implementation.
I'll see if I can find some time this weekend...
MortenMacFly:
--- Quote from: oBFusCATed on August 25, 2010, 02:08:51 am ---Great, I'll see what I can do to fix them:)
--- End quote ---
You are the first person I know saying "Great" if a bug is found. :lol: :lol: :lol:
oBFusCATed:
--- Quote from: MortenMacFly on August 27, 2010, 08:41:06 am ---You are the first person I know saying "Great" if a bug is found. :lol: :lol: :lol:
--- End quote ---
I say "Great", when I know how to reproduce a bug, because most of the work is done at this time.
oBFusCATed:
--- Quote from: pfong on August 24, 2010, 11:18:53 pm ---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.
--- End quote ---
This does not happen in my tests. C::B sends the correct continue command, when I'm remote debugging.
I've tested on windows and linux, both worked.
I've tested with CB from the debuggers branch.
--- Quote from: pfong on August 24, 2010, 11:18:53 pm ---Are you also asking if the stop button not working depends on it being a remote target?
--- End quote ---
The stop but happens for me too...
Edit: If you can't fix the continue/run problem please provide simple example project, please setup it to connect to localhost:1234 and specify all steps required to reproduce the problem...
pfong:
--- Quote from: oBFusCATed on August 29, 2010, 09:18:04 pm ---This does not happen in my tests. C::B sends the correct continue command, when I'm remote debugging.
I've tested on windows and linux, both worked.
I've tested with CB from the debuggers branch.
Edit: If you can't fix the continue/run problem please provide simple example project, please setup it to connect to localhost:1234 and specify all steps required to reproduce the problem...
--- End quote ---
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.
The workaround I've been using is to use
"define run
continue
end"
in the GDB initialization to redefine run to be the same as continue.
--- Quote from: oBFusCATed on August 29, 2010, 09:18:04 pm ---
--- Quote from: pfong on August 24, 2010, 11:18:53 pm ---Are you also asking if the stop button not working depends on it being a remote target?
--- End quote ---
The stop but happens for me too...
--- End quote ---
Are you saying it works correctly (stops the program) or that it is broken (prints out "Trying to pause running process..." and nothing happens)?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version