From: Chris Packham <judge.packham@gmail.com>
To: Simon Sobisch <simonsobisch@gnu.org>
Cc: GDB Mailing list <gdb@sourceware.org>
Subject: Re: Is there an option to "silent-step"/ "silent-next" (possibly in python and/or mi)?
Date: Thu, 9 Feb 2023 20:00:49 +1300 [thread overview]
Message-ID: <CAFOYHZAmqoJ40bGxkiP3roE3WUZoyeO4jTWTX9MiomoNyk6zXQ@mail.gmail.com> (raw)
In-Reply-To: <36c20830-7713-bff5-ca88-ea8bc2aab8b5@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
On Thu, 9 Feb 2023, 2:44 AM Simon Sobisch via Gdb, <gdb@sourceware.org>
wrote:
> For "stepping in the current source" (given a mixed-source) I look for a
> way to "silent step" / "silent next".
> This will be useful for example if you debug within Bison and/or Flex
> generated sources and don't want to step through the state / token
> machine, having only the Bison / Flex _source_ be visible.
>
> Getting the source name from the frame and comparing this after a
> step/next is no big problem in GDB using python
> gdb.selected_frame().find_sal().symtab.fullname()
>
> Using GDB in TUI mode I commonly "stay" in the source I'm interested in
> this way, but the GDB command line gets "flooded" with all the
> intermediate frame positions I'm not interested in.
>
> So: is there a way to do a "step"/"next" with suppressing the normal
> output and mi stop events normally send?
>
> Thank you for any pointers,
> Simon
>
Does the `skip` command do what you want? I use it for skipping
uninteresting things like memset() or printf() when stepping.
>
next prev parent reply other threads:[~2023-02-09 7:01 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 [this message]
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
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=CAFOYHZAmqoJ40bGxkiP3roE3WUZoyeO4jTWTX9MiomoNyk6zXQ@mail.gmail.com \
--to=judge.packham@gmail.com \
--cc=gdb@sourceware.org \
--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).