From: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>,
Simon Sobisch <simonsobisch@gnu.org>
Cc: Tom Tromey <tom@tromey.com>,
Philippe Waroquiers <philippe.waroquiers@skynet.be>
Subject: RE: Is there an option to "silent-step"/ "silent-next" (possibly in python and/or mi)?
Date: Mon, 13 Feb 2023 07:38:08 +0000 [thread overview]
Message-ID: <DM4PR11MB73033ECF0A7D9FCC8BC5C068C4DD9@DM4PR11MB7303.namprd11.prod.outlook.com> (raw)
In-Reply-To: <f54e9e2cc874c8592260b8917ba6e576ae71733e.camel@skynet.be>
On Sunday, February 12, 2023 6:23 PM, Philippe Waroquiers wrote:
> At least some of the output is discarded:
> (gdb) alias wwww = | next | cat > /dev/null
> (gdb) n
> 33 for (int i = 0; i < MAX/3; i++)
> (gdb) wwww
> (gdb)
>
> Philippe
>
>
> On Sun, 2023-02-12 at 07:46 -0700, Tom Tromey wrote:
> > 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
>
There is "set suppress-cli-notifications". Does it satisfy the needs?
(gdb) set suppress-cli-notifications on
(gdb) step
(gdb) next
(gdb) next
(gdb) next
(gdb)
Regards,
-Baris
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
prev parent reply other threads:[~2023-02-13 7:38 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
2023-02-12 17:22 ` Philippe Waroquiers
2023-02-13 7:38 ` Aktemur, Tankut Baris [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=DM4PR11MB73033ECF0A7D9FCC8BC5C068C4DD9@DM4PR11MB7303.namprd11.prod.outlook.com \
--to=tankut.baris.aktemur@intel.com \
--cc=gdb@sourceware.org \
--cc=philippe.waroquiers@skynet.be \
--cc=simonsobisch@gnu.org \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).