From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH, gdb6.8] -break-list doesn't list multiple breakpoints
Date: Thu, 03 Apr 2008 10:45:00 -0000 [thread overview]
Message-ID: <18420.41316.87382.142756@kahikatea.snap.net.nz> (raw)
In-Reply-To: <ft25eb$4la$1@ger.gmane.org>
> > Using the bkptno field means that existing frontends will recognise these
> > locations as breakpoints.
>
> Yes, but those are not a breakpoints, do it will do a disservice to the
> existing frontends. In particular, might find it very interesting experience
> to edit condition of one breakpoint, and having conditions on other
> breakpoints change. Likewise, changing any properly of location will not
> work.
>
> I think that right now, the only thing that existing frontend cannot do is
> to individually disable and enable locations. This is nice thing to have,
> but not very critical, so I think it's fine for only new frontends to have
> this capability, given the presenting locations as breakpoints comes with a
> bunch of issues.
If set individually, the multiple breakpoint locations can be used with
deleted, ignore, condition and commands. Why would this not true when the
location is part of a multiple breakpoint? Is it just due to the
implementation or a fundamental limitation?
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-04-03 9:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 17:16 Bogdan Slusarczyk
2008-04-03 5:42 ` Nick Roberts
2008-04-03 6:44 ` Vladimir Prus
2008-04-03 9:21 ` Nick Roberts
2008-04-03 10:00 ` Vladimir Prus
2008-04-03 10:45 ` Nick Roberts [this message]
2008-04-03 10:49 ` Vladimir Prus
2008-04-03 11:28 ` Nick Roberts
2008-04-03 11:39 ` Vladimir Prus
2008-04-03 11:52 ` Bogdan Slusarczyk
2008-04-03 12:12 ` Vladimir Prus
2008-04-03 12:48 ` Bogdan Slusarczyk
2008-04-14 18:22 ` Daniel Jacobowitz
2008-04-15 8:35 ` Vladimir Prus
2008-04-15 20:13 ` Bogdan Slusarczyk
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=18420.41316.87382.142756@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb-patches@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