Very slightly modified take#2 committed.
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.d
On Wed, Sep 23, 2009 at 10:39 PM, Michael Schwingen
wrote:
> Øyvind Harboe wrote:
>> I loathe options perhaps we can add some if we have to.
>>
> That is OK with me.
>> The old behavior is kinda buggy What alternative behavior
>> do you have in mind?
>>
> I have no better idea - if this wo
Øyvind Harboe wrote:
> I loathe options perhaps we can add some if we have to.
>
That is OK with me.
> The old behavior is kinda buggy What alternative behavior
> do you have in mind?
>
I have no better idea - if this works as proposed (ie. the change does
not cause problems with debu
On Wed, Sep 23, 2009 at 7:04 PM, Michael Schwingen
wrote:
> Øyvind Harboe wrote:
>> Patch attached.
>>
>> 1. The first "stepi/continue" after a connect will return immediately
>> without affecting the state of the target. This allows GDB to sync
>> up to the target state. Nice when wanting to atta
Øyvind Harboe wrote:
> Patch attached.
>
> 1. The first "stepi/continue" after a connect will return immediately
> without affecting the state of the target. This allows GDB to sync
> up to the target state. Nice when wanting to attach GDB to
> a running target and deciding using GDB monitor comman
I just realized that we can print out some messages when
handling the stepi/continue packets to inform the GDB
user what's happening.
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
### Eclipse Workspace Patch 1.0
#P openocd
Ind
Patch attached.
1. The first "stepi/continue" after a connect will return immediately
without affecting the state of the target. This allows GDB to sync
up to the target state. Nice when wanting to attach GDB to
a running target and deciding using GDB monitor commands how
to start examining/haltin
I'm wondering if it would be a good idea to modify the handling
of GDB halted/running state as follows:
- do nothing upon attaching GDB to OpenOCD. This gives
the GDB init script more freedom w.r.t. what should happen
when connecting to the target.
- if the target is running and GDB is halted, the
