From: Frederic Marmond <fmarmond@eprocess.fr>
To: ssams sudin <sams@linuxmail.org>
Cc: linux-assembly@vger.kernel.org
Subject: Re: ELF binarry
Date: Wed, 15 Oct 2003 08:39:34 +0200 [thread overview]
Message-ID: <3F8CEBA6.3020706@eprocess.fr> (raw)
In-Reply-To: <20031014152812.24625.qmail@linuxmail.org>
ssams sudin wrote:
>with GDB or another debugger, can we look at highest memory address of ELF binarry.
>if yes what is the command ?
>where can i found some reference about it?
>
>forgive me if this subject out of topic or just repeating last post
>regard
>ssams
>
>
You may find usefull to see all infos about your elf with the 'readelf'
tool.
$ readelf -a /bin/dd
will display a lot of interesting thing about where is what (but it is
oriented to shared libraries though...)
It is usefull to see the basic organisation of a program, before
starting debug it.
Fred
next prev parent reply other threads:[~2003-10-15 6:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 15:28 ELF binarry ssams sudin
2003-10-14 17:04 ` Brian Raiter
2003-10-15 6:39 ` Frederic Marmond [this message]
[not found] <20031015160137.8874.qmail@linuxmail.org>
2003-10-15 21:56 ` Brian Raiter
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=3F8CEBA6.3020706@eprocess.fr \
--to=fmarmond@eprocess.fr \
--cc=linux-assembly@vger.kernel.org \
--cc=sams@linuxmail.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 NNTP newsgroup(s).