Re: sid debugger interface extension: step out-of-range packet support

[Piet/Pete Delaney <piet@sgi.com>]

On Wed, Feb 13, 2002 at 01:10:45AM -0500, Andrew Cagney wrote:
> >Hi -
> >
> >A small amount of new code in sid/include and sid/component/gdb
> >now allows gdb's "step out-of-range" packet ('e'/'E') to work with
> >all sid-based simulator targets.  This packet makes remote debugging
> >potentially significantly faster, because it can replace a sequence of
> >instruction single-step packets with just one new packet.  This finally
> >exercises J.T. Conklin's gdb-side extensions from roughly a year ago.
> >
> >There is a gdb bug that is exposed by this support.  If a breakpoint
> >placed on the current instruction, and another one on the next
> >source line, then letting gdb "step" will stop at the next line, but
> >won't let gdb realize that the second breakpoint was hit.  (This is
> >because gdb never inserted the breakpoints in gdb/infrun.c's proceed(),
> >being unaware that remote_resume() meant something other than stepi.)
> >This looks like this is a minor problem, but just in case, support for
> >the packet may be forced off from the gdb side and/or from the sid side.
> 
> 
> Just to be clear.  I wouldn't rely to much on that current packet and/or 
> implementation.  A number of issues with it have been pointed out with 
> it.  Suggest looking through the archives.

I found Frank more clear.

-piet