From: "russell at shotover dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/30589] debuginfod can't find sources even though they exist on disk
Date: Tue, 27 Jun 2023 00:23:49 +0000 [thread overview]
Message-ID: <bug-30589-10460-13ktc3sgCQ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30589-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30589
--- Comment #1 from Russell Greene <russell at shotover dot com> ---
er, the correct command for the non-working case should be
DEBUGINFOD_URLS="http://localhost:8002" debuginfod-find source
aaaaaaaaaabbbbbbbbbbccccccccccdddddddddd `pwd`/servefrom/test.c
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-06-27 0:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 0:21 [Bug debuginfod/30589] New: " russell at shotover dot com
2023-06-27 0:23 ` russell at shotover dot com [this message]
2023-06-27 0:52 ` [Bug debuginfod/30589] " fche at redhat dot com
2023-06-27 2:20 ` russell at shotover dot com
2023-06-27 4:33 ` russell at shotover 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-30589-10460-13ktc3sgCQ@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).