From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 849 invoked by alias); 17 Mar 2006 17:23:00 -0000 Received: (qmail 840 invoked by uid 22791); 17 Mar 2006 17:23:00 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Fri, 17 Mar 2006 17:22:58 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1FKIf8-0004CL-3u; Fri, 17 Mar 2006 12:22:54 -0500 Date: Fri, 17 Mar 2006 17:34:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: David Daney , Nick Roberts , gdb@sources.redhat.com, Vladimir Prus Subject: Re: MI: changing breakpoint location Message-ID: <20060317172254.GB15128@nevyn.them.org> Mail-Followup-To: Eli Zaretskii , David Daney , Nick Roberts , gdb@sources.redhat.com, Vladimir Prus References: <17433.61359.500131.182453@kahikatea.snap.net.nz> <20060316231215.GA25222@nevyn.them.org> <4419F35D.6000907@avtrex.com> <20060316232533.GA25722@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-03/txt/msg00129.txt.bz2 On Fri, Mar 17, 2006 at 01:42:46PM +0200, Eli Zaretskii wrote: > > 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. > > But we can ask the CLI users to type the line difference, can we? I > don't expect this command to be used too frequently from the command > line, so it doesn't seem to harsh a limitation. Would that be useful? Here's how I envision this command being useful: the context-sensitive analysis I described earlier. Heuristics (i.e. guesses) as to what's happened to the file, while GDB's back was turned. The user's rarely going to know "oh, that breakpoint moved twenty lines". The alternative command, "oh, that breakpoint should be over here now", is a lot simpler for a CLI user to use. Maybe it's still useful? I didn't think so originally, but I'm being persuaded. -- Daniel Jacobowitz CodeSourcery