At Wed, 07 Mar 2012 22:04:50 +0100, Chris Liechti wrote:
> i was just thinking about that. maybe the server could send a packet
> with register update on "monitor reset".
>
> unfortunately, it looks like "Stop Reply Packets" ("T") are not expected
> when monitor commands are issued, at least there is no suitable "stop
> reason" defined for such a case (see [1]).
>
> there is also a "process terminated" packet ("X") which seems to be
> supported at any time. it would also be reasonable, as a target reset is
> like a kill signal on a normal process on the PC -- running/continuing
> again needs restarting the process. however it's mentioned under [1],
> that this packet is not supported on all targets.
Just tried this, but it doesn't seem to have any effect as far as I
can tell.
The other problem is that neither GDB nor the server are aware of
what's being executed in a monitor command (they're passed through to
the normal mspdebug command handler). It might be possible to implement
something sensible by changing the behaviour of "kill".
- Daniel
--
D.L. Beer Engineering
www.dlbeer.co.nz
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
