From: "s.srinivas" <srinivas.surabhi@wipro.com>
To: linux-kernel@vger.kernel.org
Subject: how to see .so contents
Date: Tue, 11 Sep 2001 23:18:18 +0530 [thread overview]
Message-ID: <3B9E4E62.494FBAE4@wipro.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 301 bytes --]
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 .
thank u all in advance.
regards
srinivas
[-- Attachment #2: Wipro_Disclaimer.txt --]
[-- Type: text/plain, Size: 853 bytes --]
The Information contained and transmitted by this E-MAIL is proprietary to Wipro and/or its Customer and is intended
for use only by the individual or entity to which it is addressed, and may contain information that is privileged,
confidential or exempt from disclosure under applicable law. If this is a forwarded message, the content of this
E-MAIL may not have been sent with the authority of the Company. If you are not the intended recipient, an agent
of the intended recipient or a person responsible for delivering the information to the named recipient, you are
notified that any use, distribution, transmission, printing, copying or dissemination of this information in any way
or in any manner is strictly prohibited. If you have received this communication in error, please delete this mail &
notify us immediately at mailadmin@wipro.com
next reply other threads:[~2001-09-11 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-11 17:48 s.srinivas [this message]
2001-09-11 14:51 ` how to see .so contents Petr Baudis
2001-09-11 16:44 ` Ken Williams
-- 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=3B9E4E62.494FBAE4@wipro.com \
--to=srinivas.surabhi@wipro.com \
--cc=linux-kernel@vger.kernel.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