This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: MI: changing breakpoint location

From: Daniel Jacobowitz <drow at false dot org>
To: David Daney <ddaney at avtrex dot com>
Cc: Nick Roberts <nickrob at snap dot net dot nz>, Vladimir Prus <ghost at cs dot msu dot su>, gdb at sources dot redhat dot com
Date: Thu, 16 Mar 2006 18:25:33 -0500
Subject: Re: MI: changing breakpoint location
References: <dvc0k6$fgm$1@sea.gmane.org> <17433.61359.500131.182453@kahikatea.snap.net.nz> <20060316231215.GA25222@nevyn.them.org> <4419F35D.6000907@avtrex.com>

On Thu, Mar 16, 2006 at 03:23:09PM -0800, David Daney wrote:
> I can't see why you would want to do it anyplace *other* than the 
> editor.  It would know for sure which lines had been added and deleted. 
>  Anything else would just be guessing.

Well, in the CLI GDB, we don't have any interaction with the editor. 
So I can see the benefit in guessing.

I'm not so sure about the MI case though.  Maybe whatever conclusion
we reach should end up in the MI documentation somewhere - this sounds
like the sort of design issue that most frontends would stop to
consider...

-- 
Daniel Jacobowitz
CodeSourcery

Follow-Ups:
- Re: MI: changing breakpoint location
  - From: Eli Zaretskii

References:
- MI: changing breakpoint location
  - From: Vladimir Prus
- MI: changing breakpoint location
  - From: Nick Roberts
- Re: MI: changing breakpoint location
  - From: Daniel Jacobowitz
- Re: MI: changing breakpoint location
  - From: David Daney

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]