public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "wyatt.epp at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug cli/17997] New: save skips to a file Date: Thu, 19 Feb 2015 16:09:00 -0000 [thread overview] Message-ID: <bug-17997-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=17997 Bug ID: 17997 Summary: save skips to a file Product: gdb Version: unknown Status: NEW Severity: enhancement Priority: P2 Component: cli Assignee: unassigned at sourceware dot org Reporter: wyatt.epp at gmail dot com Similar to how breakpoints and tracepoints can be saved to a file for loading later, I'd like to be able to save skipped functions and files to a file that can be loaded in a different session. This covers similar territory to bug #15814 and bug #17442, but the finer-grained control over what is skipped and when would be useful for me. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2015-02-18 15:09 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-19 16:09 wyatt.epp at gmail dot com [this message] 2023-01-24 0:17 ` [Bug cli/17997] " 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-17997-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: linkBe 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).