Re: Save the length of inserted breakpoints

[Daniel Jacobowitz <drow@false.org>]

On Sat, Mar 04, 2006 at 09:34:55AM +1100, Steven Johnson wrote:
> I wouldn't have thought the design unfortunate.  One original aim of the
> target stubs (as i understand it) was to be able to keep them simple and
> minimal.  That would include minimizing their memory requirements. 
> Requiring a stub to store state about current breakpoints inserted would
> be a potentially big memory requirement, because how many breakpoints is
> the user going to insert? 1, 2, 50, 100's?  Or do the stubs just limit
> it, and say, i'm a simple stub, i can only have 5 breakpoints, try
> adding 6 and I'll fail? 

Wrong layer: I'm talking about entirely within GDB, rather than
between GDB and the stub.  I took it as a given that we needed to be
able to tell the remote target z0,2 or z0,4, so the remote layer would
have to cache the data itself.

-- 
Daniel Jacobowitz
CodeSourcery