From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/28284] support description functionality through HEAD
Date: Wed, 10 Nov 2021 14:17:12 +0000 [thread overview]
Message-ID: <bug-28284-10460-UMNXTTboVX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28284-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28284
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at klomp dot org
--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
A suggested C api was discussed here:
https://sourceware.org/pipermail/elfutils-devel/2021q4/004239.html
(see also the whole thread in the previous quarter)
/* Get info about an debuginfod artifact. Used to know whether
the target is already in local cache or whether it can be retrieved
from one if the urls contained in $DEBUGINFOD_URLS.
If build_id_len == 0, the build_id is supplied as a lowercase
hexadecimal string; otherwise it is a binary blob of given length.
If the requested resource is in cache, return a file descriptor
which an be used as is. If the requested resource can be found
through one of the DEBUGINFOD_URLS then -1 is returned and
file_size and transfer_size are set to the number of bytes of
the target file and the number if bytes that need to be transferred
from the server (file_size is the uncompressed size, transfer_size
might be the compressed size). Otherwise return -2 to indicate the
requested artifact cannot be found.
If the file wasn't in cache, but can be retrieved from a remote
server, then debuginfod_get_url () will return where the target
can be found. A successive debuginfod_find_* call will retieve
the resource (unless a network error occurs). */
int debuginfod_info_debuginfo (debuginfod_client *client,
const unsigned char *build_id,
int build_id_len,
size_t *size, size_t *transfer_size);
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-11-10 14:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 19:02 [Bug debuginfod/28284] New: " nsanci at redhat dot com
2021-08-27 19:02 ` [Bug debuginfod/28284] " nsanci at redhat dot com
2021-08-27 19:05 ` fche at redhat dot com
2021-11-10 14:17 ` mark at klomp dot org [this message]
2022-01-20 0:17 ` fche at redhat dot com
2022-05-16 18:55 ` nsanci at redhat dot com
2022-08-11 12:50 ` fche at redhat dot com
2022-08-12 9:05 ` mliska at suse dot cz
2022-09-07 23:16 ` 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-28284-10460-UMNXTTboVX@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).