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: Nick Roberts <nickrob at snap dot net dot nz>
Cc: Vladimir Prus <ghost at cs dot msu dot su>, gdb at sources dot redhat dot com
Date: Thu, 16 Mar 2006 18:56:44 -0500
Subject: Re: MI: changing breakpoint location
References: <dvc0k6$fgm$1@sea.gmane.org> <17433.61359.500131.182453@kahikatea.snap.net.nz>

On Fri, Mar 17, 2006 at 12:07:27PM +1300, Nick Roberts wrote:
>  > Now, I have to delete the old breakpoint and create the new one, which is
>  > workable, but not convenient.
> 
> I don't find a problem with that, but it would be nice if when a program is
> edited and recompiled that GDB could track the line number.  So, for example
> if the breakpoint is on line 10, say, and lines 4 and 5 are deleted, then
> after recompiling and restarting, its on line 8.  I think Visual Stuio has
> this feature.  I have no idea how easy/hard it would be to implement.

BTW, this does make me think about the original request differently; it
does seem a bit awkward to have to delete and recreate breakpoints
every time the user edits a source file.  Maybe it isn't.  I don't
know...

-- 
Daniel Jacobowitz
CodeSourcery

Follow-Ups:
- Re: MI: changing breakpoint location
  - From: Joel Brobecker

References:
- MI: changing breakpoint location
  - From: Vladimir Prus
- MI: changing breakpoint location
  - From: Nick Roberts

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