From: Phil Muldoon <pmuldoon@redhat.com>
To: Frysk Hackers <frysk@sourceware.org>
Subject: Elf frysk-imports bindings change
Date: Thu, 12 Oct 2006 17:12:00 -0000 [thread overview]
Message-ID: <452E7772.9050801@redhat.com> (raw)
I've checked in a patch that extends the elf bindings in frysk-imports
to support writing back to the elf native data structures. This allows
us to construct a an elf file from Java. This is preparing the way for
writing core file from a frysk environment. I also added an elf error
lookup bindings.
Regards
Phil
2006-10-11 Phil Muldoon <pmuldoon@redhat.com>
* cni/Elf.cxx: (elf_begin): Check args to allow writing to
elf files.
(elf_get_last_error_msg): New.
(elf_get_last_error_no): New.
(elf_updatehdr): New.
(elf_init_core_header): New. Temporary.
(elf_updatephdr): New.
* Elf.java (Elf): Add a boolean constructor switch
for write/read.
(updateEHeader): New. Write Elf header back to native
structure.
(initializeCoreHeader): Temporary. Convienience function.
(updatePHeader): New. Write the program segment back to native
structure.
(getLastErrorMsg): New. Get the error message corresponding to
entry below.
(getLastErrorNo): New. Get the error number set if the last
elf function failed.
reply other threads:[~2006-10-12 17:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=452E7772.9050801@redhat.com \
--to=pmuldoon@redhat.com \
--cc=frysk@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).