From: Phil Muldoon <pmuldoon@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>, Pedro Alves <palves@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb@sourceware.org
Subject: Re: Multiple locations and breakpoints confusion.
Date: Wed, 02 May 2018 18:18:00 -0000 [thread overview]
Message-ID: <30233401-09ff-194c-d39f-b42dde9e423c@redhat.com> (raw)
In-Reply-To: <20180502164848.zamujdyebvuoxvzr@adacore.com>
On 02/05/18 17:48, Joel Brobecker wrote:
>> But if you ask me, the current output is immediately
>> understandable. I'd go for updating the manual.
>
> FWIW, that was my thinking also when I first started reading this thread.
>
I have no real strong opinions -- my purpose was to make sure the
functionality of the upcoming multiple locations patchlet for Python
breakpoints reflected that of GDB. However, seeing (y) in one of
locations of a multiple location breakpoint, even when the main or
parent breakpoint is disabled, does display contradictory
information. I understand the logic of the parent breakpoint
enablement or disablement overriding that of each location, though,
but I also can't help but think it is unclear or ambiguous to the
user when one of the locations says it is enabled when it isn't.
Cheers
Phil
next prev parent reply other threads:[~2018-05-02 18:18 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
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 [this message]
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=30233401-09ff-194c-d39f-b42dde9e423c@redhat.com \
--to=pmuldoon@redhat.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=palves@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