public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "richardg.work at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/15814] New: Improve "skip file X" behaviour in .gdbinit to allow quiet adding of skip entries
Date: Sun, 04 Aug 2013 22:06:00 -0000 [thread overview]
Message-ID: <bug-15814-4717@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=15814
Bug ID: 15814
Summary: Improve "skip file X" behaviour in .gdbinit to allow
quiet adding of skip entries
Product: gdb
Version: 7.6
Status: NEW
Severity: enhancement
Priority: P2
Component: cli
Assignee: unassigned at sourceware dot org
Reporter: richardg.work at gmail dot com
Created attachment 7134
--> http://sourceware.org/bugzilla/attachment.cgi?id=7134&action=edit
Patch for "server skip file X"
I want my gdb to always skip the system headers. But adding (say) "skip file
/usr/include/c++/4.6/debug/safe_iterator.h" to the .gdbinit file will get
ignored as there's nothing loaded at that point.
The attached patch changes the default behaviour to assume you want the skip to
apply to future loads. Also if you use "server skip file X", it will hide the
"File X will be skipped when stepping" message so you can quietly add skips.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2013-08-04 22:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-04 22:06 richardg.work at gmail dot com [this message]
2013-08-09 15:44 ` [Bug cli/15814] " tromey at redhat dot com
2020-09-02 13:36 ` trass3r at gmail dot com
2023-01-23 22:51 ` tromey at sourceware dot org
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=bug-15814-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.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).