public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/16229] New: ebfd_mtime and objfile::mtime are redundant Date: Mon, 25 Nov 2013 16:01:00 -0000 [thread overview] Message-ID: <bug-16229-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=16229 Bug ID: 16229 Summary: ebfd_mtime and objfile::mtime are redundant Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: tromey at redhat dot com ebfd_mtime and objfile::mtime are redundant now that gdb has a BFD cache. Also, some uses of these imply that the BFD cache logic is spread around gdb -- that is, the cache logic cannot simply be changed, instead all such spots must be tracked down and changed as well. One fix would be to add a new gdb_bfd_cached_mtime accessor and then update the users. Some spots, like reread_symbols, could be changed to open a new BFD via the cache and see if it has changed. -- You are receiving this mail because: You are on the CC list for the bug.
reply other threads:[~2013-11-25 16:01 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-16229-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).