Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob_rossi@cox.net>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: MI: changing breakpoint location
Date: Thu, 16 Mar 2006 15:48:00 -0000	[thread overview]
Message-ID: <20060316154357.GC30980@brasko.net> (raw)
In-Reply-To: <dvc0k6$fgm$1@sea.gmane.org>

On Thu, Mar 16, 2006 at 06:35:34PM +0300, Vladimir Prus wrote:
> 
> Hello!
> 
> At the moment, the MI interface does not allow one to change location of
> breakpoint, say to move breakpoint from main.cpp:9 to main.cpp:11.
> CLI does not support this either, but I'm interested in MI.
> 
> Was this an explicit design decision, or it just happened this way? The use
> case when it matters if when, in KDevelop, user edits the field of
> breakpoint table with the location.
> 
> Now, I have to delete the old breakpoint and create the new one, which is
> workable, but not convenient. How about adding 'change breakpoint location'
> functionality to MI?

Hi Volodya,

My initial opinion is that this does not make to much sense. The 2
different breakpoint really have nothing to do with each other.

I would think it could be possible to add a new MI command that would
allow you to arbitrarily delete, add or modify (enable/disable) as 
many breakpoints as you want. I think this would be a little more
general purpose.

Bob Rossi


  reply	other threads:[~2006-03-16 15:43 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 [this message]
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
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=20060316154357.GC30980@brasko.net \
    --to=bob_rossi@cox.net \
    --cc=gdb@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    /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