From: "Atul Talesara" <atul.talesara@nevisnetworks.com>
To: <gdb@sources.redhat.com>
Subject: Checksum of downloaded code.
Date: Wed, 13 Oct 2004 15:35:00 -0000 [thread overview]
Message-ID: <7F17177AC9AC2F4CB4A1A33C936D038D0722A9@nevismail01.pune.nevisnetworks.com> (raw)
Hello Folks,
I've downloaded code through remote stub on my
target. Now just to check the integrity of code
downloaded, I would like to compare the checksums
computed from executable file's section data and the
actual target memory contents corresponding to that
section. Checksum of remote mem can be done by
implementing Additional GDB remote command or reading
target mem and doing checksum computation at the host
end.
I grep'ed thro' manual and google'd only to find that
there's not *simpler* way of doing this. Does anyone
know of a better way to do this or some implementation
already doing this? I found one utility named
elf32_checksum() but that's only for SUN OSes.
TIA.
Regards,
Atul P Talesara
----------------------------------------------------------
Conscience cannot prevent one from committing the crime,
It can only prevent one from enjoying it!
----------------------------------------------------------
reply other threads:[~2004-10-13 14:05 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=7F17177AC9AC2F4CB4A1A33C936D038D0722A9@nevismail01.pune.nevisnetworks.com \
--to=atul.talesara@nevisnetworks.com \
--cc=gdb@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).