Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: gdb@sources.redhat.com
Subject: Re: MI: changing breakpoint location
Date: Fri, 17 Mar 2006 10:55:00 -0000	[thread overview]
Message-ID: <dve40v$tct$1@sea.gmane.org> (raw)
In-Reply-To: <20060316231215.GA25222@nevyn.them.org>

Daniel Jacobowitz wrote:

> I'm thinking something like "remember a couple lines of context, if you
> can find the same context, adjust the breakpoint and warn the user".
> But there's some risk of it landing in the wrong place; I don't know
> how to do it reliably but I bet a motivated developer would come up
> with something :-)
> 
> Of course, then we'd have to let the MI interpreter know about the
> change too, so that the editor could refresh.  I have no idea whether
> GUIs would want this behavior or not; wouldn't they want to track it
> themselves assuming you used the GUI's editor?

I think that automatic moving of breakpoints is better done in GUI. GUI has
more data, including specific set of editing operations, and it has more
feedback mechanisms, it can even show dialog box "This breakpoint was
moved, if that OK?", after all.

GDB, on the other hand, can only guess right breakpoint positions based on
analysing the source. And imagine you type in comment right before
breakpoint position. This will break all context-based analysis.

- Volodya





  parent reply	other threads:[~2006-03-17 10:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-16 15:43 Vladimir Prus
2006-03-16 15:48 ` Bob Rossi
2006-03-16 16:05   ` Vladimir Prus
2006-03-16 16:12 ` Daniel Jacobowitz
2006-03-16 16:16   ` Vladimir Prus
2006-03-16 16:40     ` Daniel Jacobowitz
2006-03-16 16:46       ` Vladimir Prus
2006-03-16 17:11         ` Daniel Jacobowitz
2006-03-17 10:46           ` Vladimir Prus
2006-03-17 18:28             ` Daniel Jacobowitz
2006-03-17 17:43               ` Daniel Jacobowitz
2006-03-17 11:03       ` Eli Zaretskii
2006-03-17 10:57   ` Eli Zaretskii
2006-03-16 23:12 ` Nick Roberts
2006-03-16 23:23   ` Daniel Jacobowitz
2006-03-16 23:25     ` David Daney
2006-03-16 23:54       ` Daniel Jacobowitz
2006-03-17 13:20         ` Eli Zaretskii
2006-03-17 17:34           ` Daniel Jacobowitz
2006-03-18 18:46             ` Eli Zaretskii
2006-03-16 23:56       ` Nick Roberts
2006-03-17 10:55     ` Vladimir Prus [this message]
2006-03-17 11:42     ` Eli Zaretskii
2006-03-17  0:04   ` Daniel Jacobowitz
2006-03-17  0:23     ` Joel Brobecker
2006-03-17  3:57       ` Jim Ingham
2006-03-17 11:40   ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='dve40v$tct$1@sea.gmane.org' \
    --to=ghost@cs.msu.su \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox