From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/30241] RFE add APIs to elfutis libdw
Date: Fri, 17 Mar 2023 17:32:50 +0000 [thread overview]
Message-ID: <bug-30241-10460-dGyxYxPYoa@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30241-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30241
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
This depends largely on what sort of editing API a client envisions.
Writing brand new content from scratch is more like an assembler task.
Making micro edits in situ (changing individual DIEs, insert/delete, like a
text editor) is likely to be entirely different and much more complicated.
So ISTM this needs to be drive not by elfutils in the abstract but the specific
needs of the editing/synthesis tools.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-03-17 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 17:23 [Bug general/30241] New: " woodard at redhat dot com
2023-03-17 17:32 ` fche at redhat dot com [this message]
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-30241-10460-dGyxYxPYoa@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).