From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [BUG:MI] -break-list doesn't list multiple breakpoints
Date: Wed, 30 Jan 2008 07:50:00 -0000 [thread overview]
Message-ID: <18336.10418.671118.355348@kahikatea.snap.net.nz> (raw)
In-Reply-To: <fnp8jj$hl3$1@ger.gmane.org>
> Given that such a change has a potential to totally break frontend,
> I'm not sure we can talk in the abstract. If you send me the most
> recent version of your patch, I can see if KDevelop will be happy,
> or not.
It's been a long thread and maybe I've lost the plot but I'm just talking
about the simple change below now.
--
Nick http://www.inet.net.nz/~nickrob
*** breakpoint.c.~1.299.~ 2008-01-30 11:59:18.000000000 +1300
--- breakpoint.c 2008-01-30 20:32:30.000000000 +1300
*************** print_one_breakpoint (struct breakpoint
*** 3669,3676 ****
exposed to user. */
if (b->loc
&& !is_hardware_watchpoint (b)
! && (b->loc->next || !b->loc->enabled)
! && !ui_out_is_mi_like_p (uiout))
{
struct bp_location *loc;
int n = 1;
--- 3669,3675 ----
exposed to user. */
if (b->loc
&& !is_hardware_watchpoint (b)
! && (b->loc->next || !b->loc->enabled))
{
struct bp_location *loc;
int n = 1;
next prev parent reply other threads:[~2008-01-30 7:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 22:08 Nick Roberts
2008-01-11 17:36 ` Vladimir Prus
2008-01-11 21:34 ` Nick Roberts
2008-01-11 22:55 ` Daniel Jacobowitz
2008-01-11 23:38 ` Nick Roberts
2008-01-15 17:08 ` Vladimir Prus
2008-01-15 21:38 ` Nick Roberts
2008-01-13 21:26 ` Nick Roberts
2008-01-29 19:16 ` Daniel Jacobowitz
2008-01-29 22:53 ` Nick Roberts
2008-01-29 23:31 ` Daniel Jacobowitz
2008-01-30 0:52 ` Nick Roberts
2008-01-30 3:04 ` Nick Roberts
2008-01-30 3:20 ` Daniel Jacobowitz
2008-01-30 5:59 ` Vladimir Prus
2008-01-30 7:14 ` Nick Roberts
2008-01-30 7:32 ` Vladimir Prus
2008-01-30 7:50 ` Nick Roberts [this message]
2008-01-30 7:58 ` Vladimir Prus
2008-02-01 20:15 ` Marc Khouzam
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=18336.10418.671118.355348@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