From: "H. J. Lu" <hjl@lucon.org>
To: "André Hauser" <aphauser@gmx.de>
Cc: binutils@sources.redhat.com
Subject: Re: Change an object file without explicit copying
Date: Sun, 07 Jul 2002 12:45:00 -0000 [thread overview]
Message-ID: <20020707073614.A23481@lucon.org> (raw)
In-Reply-To: <19236.1026021655@www29.gmx.net>; from aphauser@gmx.de on Sun, Jul 07, 2002 at 08:00:55AM +0200
On Sun, Jul 07, 2002 at 08:00:55AM +0200, André Hauser wrote:
> Dear forum,
> I want to use bfd to update an existing ELF file, i.e. open a bfd,
> perform some changes and save the file afterwards.
> Is there a way of doing this without copying the source file? I found
> only the two functions bfd_openw() and bfd_openr() for creating a new
> resp. opening a bfd; calling bfd_make_writable() in conjunction with
> bfd_openr() did not work, my object file wasn't updated after closing
> the bfd.
>
Have you tried libelf?
H.J.
next prev parent reply other threads:[~2002-07-07 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-07 2:07 André Hauser
2002-07-07 12:45 ` H. J. Lu [this message]
2002-07-10 3:09 andre_hauser
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=20020707073614.A23481@lucon.org \
--to=hjl@lucon.org \
--cc=aphauser@gmx.de \
--cc=binutils@sources.redhat.com \
/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).