public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Tom Tromey <tom@tromey.com>
Cc: 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 18:22:58 +0100	[thread overview]
Message-ID: <f54e9e2cc874c8592260b8917ba6e576ae71733e.camel@skynet.be> (raw)
In-Reply-To: <87sffbeyar.fsf@tromey.com>

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



  reply	other threads:[~2023-02-12 17:23 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 [this message]
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=f54e9e2cc874c8592260b8917ba6e576ae71733e.camel@skynet.be \
    --to=philippe.waroquiers@skynet.be \
    --cc=gdb@sourceware.org \
    --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).