Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Nick Roberts <nickrob@snap.net.nz>,
		Vladimir Prus <ghost@cs.msu.su>,
	gdb@sources.redhat.com
Subject: Re: MI: changing breakpoint location
Date: Fri, 17 Mar 2006 00:23:00 -0000	[thread overview]
Message-ID: <20060317000417.GJ702@adacore.com> (raw)
In-Reply-To: <20060316235644.GA26469@nevyn.them.org>

> 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...

Just my few cents:

To me, it was initially expected and normal. But then there are some
issues GUIs have to be careful of, probably derived from the fact that
the new breakpoint would have a different ID. They have to transfer
over conditions expressions, command lists, etc.

For some reason I can't put my finger on, I feel against such a feature,
but then it would make things simpler for the GUI, and the user would
not be confused by a different breakpoint number when the location
is modified...

Doesn't seem like something that would be too hard to implement either,
right? Something like "move-breakpoint break-id new-location". If it
added to GDB, I would make it available for CLI as well, might as well.

-- 
Joel


  reply	other threads:[~2006-03-17  0:04 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
2006-03-17 11:42     ` Eli Zaretskii
2006-03-17  0:04   ` Daniel Jacobowitz
2006-03-17  0:23     ` Joel Brobecker [this message]
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=20060317000417.GJ702@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    --cc=nickrob@snap.net.nz \
    /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