public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "levi.armstrong at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/18531] New: Request to add functionality "set skip pending on"
Date: Sat, 13 Jun 2015 03:53:00 -0000	[thread overview]
Message-ID: <bug-18531-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=18531

            Bug ID: 18531
           Summary: Request to add functionality "set skip pending on"
           Product: gdb
           Version: 7.7
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: levi.armstrong at gmail dot com
  Target Milestone: ---

Currently if you add the command skip file or skip function withing the
.gdbinit you will receive the output below resulting in the file or function
not being added. I think it would be very use full to the feature set skip
pending on similar to the set breakpoint pending on to allow for you to add the
skip files to the .gdbinit file or in my case the IDE I am using will execute a
python script that will loop through and add all of the boost headers to the
skip.

No source file named ".........."
~"Ignore file pending future shared library load? (y or [n])[answered N; input
not from terminal]\n"

I am interested in help with the development of the patch but I am not familiar
with the gdb source, so I would need assistance in how to best implement this
patch.

Thank you for your time.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2015-06-13  3:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-13  3:53 levi.armstrong at gmail dot com [this message]
2015-06-14  4:47 ` [Bug gdb/18531] " levi.armstrong at gmail dot com

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-18531-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).