public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/27678] New: [gdb/symtab] Use debuginfod sourcelist api to test for file existence Date: Thu, 01 Apr 2021 06:06:16 +0000 [thread overview] Message-ID: <bug-27678-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=27678 Bug ID: 27678 Summary: [gdb/symtab] Use debuginfod sourcelist api to test for file existence Product: gdb Version: HEAD Status: NEW Severity: enhancement Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- Spinoff of PR27667. In PR27673, a new debuginfod webapi to is proposed to enumerate source files: a "/buildid/HEXCODE/sourcelist" query. Once that's there, the client api could be extended to support an debuginfod_source_exists_query. This could then be used in gdb. Currently in gdb, in some cases (symtab_to_fullname) we just want to know whether the file exists, and in order to verify this we open the file using debuginfod_source_query, test the resulting file descriptor for success and then close it. This means sending over the content of the file, but not immediately using it. Using debuginfod_source_exists_query would be cheaper. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-04-01 6:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-01 6:06 vries at gcc dot gnu.org [this message] 2021-04-01 6:06 ` [Bug symtab/27678] " vries at gcc dot gnu.org 2022-01-19 23:50 ` fche at redhat 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-27678-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).