From: Tom Tromey <tom@tromey.com>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: Tom Tromey <tom@tromey.com>,
Simon Sobisch via Gdb <gdb@sourceware.org>,
Simon Sobisch <simonsobisch@gnu.org>
Subject: Re: Is there an option to "silent-step"/ "silent-next" (possibly in python and/or mi)?
Date: Sun, 12 Feb 2023 07:46:52 -0700 [thread overview]
Message-ID: <87sffbeyar.fsf@tromey.com> (raw)
In-Reply-To: <6628499778f82e95775922af04cb397a16d33cd7.camel@skynet.be> (Philippe Waroquiers's message of "Sun, 12 Feb 2023 13:38:33 +0100")
Philippe> As a (not very clean) bypass, you might do something like:
Philippe> alias silent-next = | next | grep -e some_regexp_to_see what_you_are_interested_in
Philippe> and if you want to see nothing:
Philippe> alias silent-next = | next | cat > /dev/null
I'm not completely sure but I think some of the inferior-control
commands work in a way that circumvents this. At least, IIRC, there's a
bug open about not being able to capture this output using
gdb.execute(to_string=True).
Tom
next prev parent reply other threads:[~2023-02-12 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 13:44 Simon Sobisch
2023-02-09 7:00 ` Chris Packham
2023-02-09 8:36 ` Simon Sobisch
2023-02-10 16:59 ` Tom Tromey
2023-02-12 12:38 ` Philippe Waroquiers
2023-02-12 14:46 ` Tom Tromey [this message]
2023-02-12 17:22 ` Philippe Waroquiers
2023-02-13 7:38 ` Aktemur, Tankut Baris
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=87sffbeyar.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb@sourceware.org \
--cc=philippe.waroquiers@skynet.be \
--cc=simonsobisch@gnu.org \
/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).