Sponsored Content
Operating Systems Linux how to backtrace a shared library file (.so) Post 302240975 by princelinux on Saturday 27th of September 2008 10:41:11 AM
Old 09-27-2008
how to backtrace a shared library file (.so)

I have a shared library file (.so) and I need to know some information
1. By which GCC version was this .so built?
2. Was this .so built in 32 bits mode or 64 bits mode

Any command / tools to backtrace such kind of information?

Thanks in advance!
 

3 More Discussions You Might Find Interesting

1. AIX

How to debug a shared library(.so file) on AIX?

How to debug a shared library(.so file) on AIX? (1 Reply)
Discussion started by: AlbertGao
1 Replies

2. UNIX for Dummies Questions & Answers

What programs access shared library file

I was curious how to tell which programs are accessing a file (libobjc.A.dylib) in /usr/lib This file seems to be the culprit in a bunch of Safari crashes, and I just wanted to know if and what other programs use it. Also, I was curious what a good way to find out what files are being written... (4 Replies)
Discussion started by: glev2005
4 Replies

3. HP-UX

Problem in Shared library file .sl on 64bit HP-UX 11.11

We are facing issue with shared library file, we are getting difference in content for same shared file for chatr command :confused: , below are the detail about *.sl file, even we are also getting difference in size of both file. can you please tell me what will be the issue for same. is my new... (1 Reply)
Discussion started by: amodkavi
1 Replies
st(1M)																	    st(1M)

NAME
st - shared tape administration SYNOPSIS
device_file DESCRIPTION
The command provides users with a command-line interface to check the status of a shared tape device or to reclaim a shared tape device from a host system that has failed while holding a reservation on the shared tape device. The command can also be used for the same pur- pose on shared library robotic devices. To use the command you must have root user id. Please see examples below for usage. Options recognizes the following options and arguments: Specifies the tape device file or sctl/esctl pass-through device file for the shared tape/library device. This parameter is mandatory and will report an error if device_file is omitted. Allows the user to reclaim a shared tape device or shared library robotic device in the case where a host failed while holding a reservation on the shared device. This option causes a bus device reset to be issued to the device specified by the option. Prints out the current status of the shared tape/library device specified by the option. RETURN VALUE
returns 0 upon successful completion and 1 otherwise. EXAMPLES
The following shows three examples of output from the above command. The above output indicates that the shared device is reserved by another host and is therefore unavailable at this time. The above output indicates that the shared device is not ready for use at this time. The above output indicates that the shared device is ready for use at this time. To reclaim a shared tape/library device from a failed host, the following command can be used: WARNINGS
The option must be used with care. When reclaiming devices, it must be ensured that the host from which the device is being reclaimed has in fact failed, as data may be lost as the result of reclaiming a device that is currently in use by another host. AUTHOR
was developed by Hewlett-Packard. SEE ALSO
mt(1), scsi(7), scsi_ctl(7). st(1M)
All times are GMT -4. The time now is 11:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy