public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: Pedro Alves <pedro@palves.net>
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:56:59 -0700	[thread overview]
Message-ID: <87pmbi4610.fsf@tromey.com> (raw)
In-Reply-To: <de0fa95d-80a5-ef50-8209-f9fcddb32d22@palves.net> (Pedro Alves's message of "Fri, 13 Jan 2023 12:59:48 +0000")

>>>>> "Pedro" == Pedro Alves <pedro@palves.net> writes:

Pedro> Wouldn't making the breakpoint "internal" work for the same effect?

No:

(gdb) python gdb.Breakpoint("nosuch", internal=True)
No symbol table is loaded.  Use the "file" command.
(gdb) python gdb.Breakpoint("nosuch", announce=False)
(gdb)

I didn't really think about it though.  I guess 'internal' could maybe
be reused to disable the other message as well.

Tom

      reply	other threads:[~2023-01-13 18:57 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
2023-01-13 12:59   ` Pedro Alves
2023-01-13 18:56     ` Tom Tromey [this message]

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=87pmbi4610.fsf@tromey.com \
    --to=tromey@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    /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).