Re: [RFA] Reverse Debugging, 1/5

[Joel Brobecker <brobecker@adacore.com>]

> >In infrun, the same as any other user supplied execution state.
> >For instance the scheduler-locking setting.
> 
> I'm ok with that, if that's what we decide.
> 
> But understand -- the target HAS to remember this state,
> so now we are duplicating state.  Unles we go back and
> reverse that very first design decision and add a parameter
> to resume -- which will be a lot of work.

I don't think that adding a parameter to resume will be beneficial
at this point.  But I think it would be beneficial to have it in
infrun instead of having the extra target method - the "target"
in GDB's sense of the target layer doesn't have to remember the
direction, since it can query infrun.  What you're saying is that
the actual target (be it some device behind the remote protocol,
or a native target, etc) will also have to remember. But I think
that's fine, and I think it's better to have this really small
duplication rather than taking the chance of sending a packet
over a slow line.  In fact, you already realized this, since you
cached the direction in the remote target layer. ;-).

-- 
Joel