Re: [Openocd-development] gdb server stepping

[Ø. H. <oyv...@zy...>]

On Tue, Sep 23, 2008 at 2:56 PM, Spen <sp...@sp...> wrote:
> Øyvind,
>
> One thing i have noticed with later versions of openocd is that every time
> you step with gdb/insight a message is sent to the console window.
> it is worse in insight because the console window will be shown on every
> step.

Fixed.



> for example a single step:
>
> target state: halted
> target halted due to single-step, current mode: Thread
> xPSR: 0x21000000 pc: 0x08000108
> target state: halted
> target halted due to single-step, current mode: Thread
> xPSR: 0x61000000 pc: 0x0800010a
> target state: halted
> target halted due to single-step, current mode: Thread
> xPSR: 0x61000000 pc: 0x0800010c
>
> This is not really desired behaviour or the original intention - not sure
> when it appeared.
> I have had a quick look through the code but the behaviour of gdb_con->busy
> has changed somewhat, so what it does now i am not sure.
>
> also just noticed that we get the following after issuing a gdb 'monitor
> help'
> Warning:BUG: keep_alive() was not invoked in the 1000ms timelimit. GDB alive
> packet not sent! (2032)
> also had a quick look but i think all this help stuff is tcl now - so unsure
> how all this works now.

Tcl was not involved. The fix was to reset the timeout value upon
sending a packet. Committed.

>
> Cheers
> Spen
>
>



-- 
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 XScale Cortex
JTAG debugger and flash programmer