User forums > Using Code::Blocks

debug plugin

(1/3) > >>

DoMeN:
Has the debug plugin been changed?
I'm not shore if I understood forum topics about this correctly but is the debug plugin broken at the moment? I've just built latest svn revision and it doesn't work for me anny more and I'm not shore if I made a misstake in settings or what.

Could somebody tell me which was the last svn revision No. before this changes?

Regards,
Domen

mandrav:

--- Quote ---I've just built latest svn revision and it doesn't work for me anny more and I'm not shore if I made a misstake in settings or what.
--- End quote ---

And if you don't tell us what exactly is not working we won't be able to help...

DoMeN:
Before I was using rev. 3300 and debugger log was:
[...]
>>>>>>cb_gdb:
> target jtag jtag://10.237.2.35:9999
load
set $pc=0x100
Remote ba debugging using jtag://10.237.2.35:9999
[...some output that jtag returns to gdb...]
 >>>>>>cb_gdb:>>>>>>cb_gdb:>>>>>>cb_gdb:
> directory /home/domenv/hello-uart/
>>>>>>cb_gdb:
> delete breakpoints
[...]

Now with rew 3536 it is:
[...]
>>>>>>cb_gdb:
target jtag jtag://10.237.2.35:9999
load
set $pc=0x100
Failed to receive SET_CHAIN response from JTAG proxy: Connection reset by peer
Remote ba debugging using jtag://10.237.2.35:9999
[...nothing...]
>>>>>>cb_gdb:>>>>>>cb_gdb:>>>>>>cb_gdb:
> directory /home/domenv/hello-uart/
You can't do that when your target is `exec'
>>>>>>cb_gdb:
> delete breakpoints
No registers.

DoMeN:
And all the settings are the same in both revisions.

mandrav:

--- Quote ---Failed to receive SET_CHAIN response from JTAG proxy: Connection reset by peer
--- End quote ---

What makes you think this is a C::B problem? C::B has nothing to do with JTAG (whatever that is). This is a message returned by the "JTAG proxy".
I 'd like some more help here, if you really think this is a C::B problem.

Navigation

[0] Message Index

[#] Next page