From: Tom Tromey <tromey@adacore.com>
To: Simon Marchi <simark@simark.ca>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] Let Python breakpoints be created silently
Date: Fri, 13 Jan 2023 11:55:38 -0700 [thread overview]
Message-ID: <87tu0u4639.fsf@tromey.com> (raw)
In-Reply-To: <3f6597da-f101-b413-f48b-2f66b77e840c@simark.ca> (Simon Marchi's message of "Thu, 12 Jan 2023 12:49:19 -0500")
>>>>> "Simon" == Simon Marchi <simark@simark.ca> writes:
>> @@ -5940,9 +5940,15 @@ the function passed in @code{spec} as a fully-qualified name. It is equivalent
>> to @code{break}'s @code{-qualified} flag (@pxref{Linespec Locations} and
>> @ref{Explicit Locations}).
>>
>> +The optional @var{announce} argument is a boolean that controls
>> +whether @var{GDBN} announces the existence of the breakpoint. The
>> +default is to announce, meaning that a message is printed. Setting
>> +this argument to false will suppress all output from breakpoint
>> +creation.
Simon> I assume this means "all CLI output", but any MI / DAP frontend would
Simon> still be notified?
Yes, I think that happens through an observer.
Tom
next prev parent reply other threads:[~2023-01-13 18:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 19:18 [PATCH 0/3] Add "announce" flag to Python breakpoint creation Tom Tromey
2022-12-08 19:18 ` [PATCH 1/3] Refactor body of bppy_init Tom Tromey
2022-12-08 19:18 ` [PATCH 2/3] Fix latent bug in Python breakpoint creation Tom Tromey
2023-01-12 17:44 ` Simon Marchi
2022-12-08 19:18 ` [PATCH 3/3] Let Python breakpoints be created silently Tom Tromey
2023-01-11 17:31 ` Tom Tromey
2023-01-12 9:42 ` Eli Zaretskii
2023-01-12 17:49 ` Simon Marchi
2023-01-13 18:55 ` Tom Tromey [this message]
2023-01-13 12:59 ` Pedro Alves
2023-01-13 18:56 ` Tom Tromey
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=87tu0u4639.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).