From: Jason Merrill <jason@redhat.com>
To: gcc-patches List <gcc-patches@gcc.gnu.org>,
Jakub Jelinek <jakub@redhat.com>
Subject: RFA: PATCH to tell gdb to skip over is-a.h inlines
Date: Mon, 25 Apr 2016 17:28:00 -0000 [thread overview]
Message-ID: <571E53C0.7040904@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 93 bytes --]
There doesn't seem to be any need to step through the is-a inline
functions. OK for trunk?
[-- Attachment #2: skip-is-a.diff --]
[-- Type: text/x-patch, Size: 603 bytes --]
commit 1b74375b17e37ab7c5f96944148ff5a6bff3f8bc
Author: Jason Merrill <jason@redhat.com>
Date: Wed Apr 20 10:21:02 2016 -0400
* gdbinit.in: Skip is-a.h.
diff --git a/gcc/gdbinit.in b/gcc/gdbinit.in
index af7d51a..d221130 100644
--- a/gcc/gdbinit.in
+++ b/gcc/gdbinit.in
@@ -246,6 +246,9 @@ set check type off
# See https://sourceware.org/gdb/current/onlinedocs/gdb/Skipping-Over-Functions-and-Files.html
skip file tree.h
+# Also skip inline functions in is-a.h.
+skip file is-a.h
+
# Likewise, skip various inline functions in rtl.h.
skip rtx_expr_list::next
skip rtx_expr_list::element
next reply other threads:[~2016-04-25 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 17:28 Jason Merrill [this message]
2016-04-25 17:30 ` Jeff Law
2016-04-28 19:04 ` Jason Merrill
2017-10-31 17:22 ` Jason Merrill
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=571E53C0.7040904@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).