From: Ken Williams <ken@tecc.co.uk>
To: srinivas.surabhi@wipro.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: how to see .so contents
Date: Tue, 11 Sep 2001 16:44:37 +0000 [thread overview]
Message-ID: <3B9E3F75.CAC7DAD2@tecc.co.uk> (raw)
In-Reply-To: <3B9E4E62.494FBAE4@wipro.com>
"s.srinivas" wrote:
>
> hi all,
>
> Its a silly question i tried with all my friends but of no use.
> Could any one tell me how to know the contents(modules) that
> are contained in any .so (shared objects) file.
>
> say for ex. for archive file ar -t .a file name is used .
I think what you want is 'objdump'
try
/usr/bin/objdump -f shared_object.so
see the man pages for more info.
Regards,
Ken
> thank u all in advance.
>
> regards
> srinivas
>
> ------------------------------------------------------------------------
> Name: Wipro_Disclaimer.txt
> Wipro_Disclaimer.txt Type: Plain Text (text/plain)
> Encoding: 7bit
next prev parent reply other threads:[~2001-09-11 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-11 17:48 how to see .so contents s.srinivas
2001-09-11 14:51 ` Petr Baudis
2001-09-11 16:44 ` Ken Williams [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-11 12:15 Rajiv Majumdar
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=3B9E3F75.CAC7DAD2@tecc.co.uk \
--to=ken@tecc.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.surabhi@wipro.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