Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: pmuldoon@redhat.com, gdb@sourceware.org
Subject: Re: Multiple locations and breakpoints confusion.
Date: Wed, 02 May 2018 15:13:00 -0000	[thread overview]
Message-ID: <83y3h2oztv.fsf@gnu.org> (raw)
In-Reply-To: <8a04e8e4-b08e-32d0-b44b-efc6f3917878@redhat.com> (message from	Pedro Alves on Tue, 1 May 2018 20:32:28 +0100)

> From: Pedro Alves <palves@redhat.com>
> Date: Tue, 1 May 2018 20:32:28 +0100
> 
> IMO, it's working as intended.

I agree that it's working as intended, but I think the UI is
confusing.

> Maybe it'd help if we would come up with some concise
> way to display a location as enabled-but-note-parent-is-disabled
> differently, like with a different letter or some extra character
> or something like that.

If disabling the parent disables all of its children, why not show all
of the children disabled when the parent is disabled?  IOW, why can't
we make the y/n display use the same logic as the one used when
deciding whether a breakpoint at a particular location is disabled?


  reply	other threads:[~2018-05-02 15:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01  8:15 Phil Muldoon
2018-05-01 19:32 ` Pedro Alves
2018-05-02 15:13   ` Eli Zaretskii [this message]
2018-05-02 16:15     ` Pedro Alves
2018-05-02 16:27       ` Pedro Alves
2018-05-02 16:42         ` Keith Seitz
2018-05-02 16:33       ` Eli Zaretskii
2018-05-02 16:43         ` Pedro Alves
2018-05-02 16:49           ` Joel Brobecker
2018-05-02 18:18             ` Phil Muldoon
2018-05-02 18:42               ` Pedro Alves

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=83y3h2oztv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=palves@redhat.com \
    --cc=pmuldoon@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