From: "christian.morales.vega at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug tools/27351] please add a debugedit binary to elfutils
Date: Fri, 05 Feb 2021 16:10:02 +0000 [thread overview]
Message-ID: <bug-27351-10460-whHXFBuqeg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27351-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27351
christian.morales.vega at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |christian.morales.vega@gmai
| |l.com
--- Comment #2 from christian.morales.vega at gmail dot com ---
I would like that, and more. I would like something doing everything
rpm/debugedit do so I can run something similar to
./extract_debuginfo_to_use_with_debuginfod -d <my_staging_dir>
So debugedit + find-debuginfo.sh +
https://github.com/rpm-software-management/rpm/commit/bbfe1f86b2e4b5c0bd499d9f3dd9de9c9c20fff2
If I could
./extract_debuginfo_to_use_with_debuginfod -d <staging_dir> -u
<my_debuginfod_server>
to directly extract+upload the debug information to my debuginfod server it
would be my ideal workflow.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-05 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 11:25 [Bug tools/27351] New: " doko at debian dot org
2021-02-05 13:28 ` [Bug tools/27351] " ldv at sourceware dot org
2021-02-05 16:10 ` christian.morales.vega at gmail dot com [this message]
2021-02-18 12:50 ` mark at klomp dot org
2021-02-19 8:15 ` mliska at suse dot cz
2021-02-19 12:20 ` pmatilai at laiskiainen dot org
2021-02-19 20:25 ` mark at klomp dot org
2021-04-26 16:19 ` mark at klomp 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-27351-10460-whHXFBuqeg@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).