From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Tom Tromey <tom@tromey.com>, Simon Sobisch via Gdb <gdb@sourceware.org>
Cc: 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 13:38:33 +0100 [thread overview]
Message-ID: <6628499778f82e95775922af04cb397a16d33cd7.camel@skynet.be> (raw)
In-Reply-To: <87o7q1xxpt.fsf@tromey.com>
As a (not very clean) bypass, you might do something like:
alias silent-next = | next | grep -e some_regexp_to_see what_you_are_interested_in
and if you want to see nothing:
alias silent-next = | next | cat > /dev/null
Philippe
On Fri, 2023-02-10 at 09:59 -0700, Tom Tromey wrote:
> > > > > > "Simon" == Simon Sobisch via Gdb <gdb@sourceware.org> writes:
>
> Simon> For "stepping in the current source" (given a mixed-source) I look for
> Simon> a way to "silent step" / "silent next".
> Simon> This will be useful for example if you debug within Bison and/or Flex
> Simon> generated sources and don't want to step through the state / token
> Simon> machine, having only the Bison / Flex _source_ be visible.
>
> Simon> Getting the source name from the frame and comparing this after a
> Simon> step/next is no big problem in GDB using python
> Simon> gdb.selected_frame().find_sal().symtab.fullname()
>
> Simon> Using GDB in TUI mode I commonly "stay" in the source I'm interested
> Simon> in this way, but the GDB command line gets "flooded" with all the
> Simon> intermediate frame positions I'm not interested in.
>
> Simon> So: is there a way to do a "step"/"next" with suppressing the normal
> Simon> output and mi stop events normally send?
>
> I don't think there is right now. I think suppressing output during
> these kinds of commands is a known issue, but nobody has looked into
> what would be needed to fix it.
>
> Tom
next prev parent reply other threads:[~2023-02-12 12: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 [this message]
2023-02-12 14:46 ` Tom Tromey
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=6628499778f82e95775922af04cb397a16d33cd7.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).