Shared Object library problem


 
Thread Tools Search this Thread
Operating Systems AIX Shared Object library problem
# 1  
Old 09-06-2006
Shared Object library problem

Hi,

When using shared objects on AIX 4.3 i am getting runtime problems.
I have a small sample program which links to a shared object libray, oracle and system related libraries.
At runtime it fails (gives segmentation fault and coredump ) in one proc file when executing login statement.

But the same program instead of using shared object library if i use archives and static linking runs fine.
What could go wrong? Any environment variable problem?
my LIBPATH variable points = "$ORACLE_HOME/lib32:$ORACLE_HOME/lib" and at linking phase i use "-L$(ORACLE_HOME)/lib32 -lc -lnsl -L$(ORACLE_HOME)/lib -lclntsh $(ORACLE_HOME)
/lib/libsql9.a -lnsl -ldl -lC -lm" arguments.

Debugging shows failure occurs when
"sqlcxt((void **)0, &sqlctx, &sqlstm, &sqlfpn);" is executed.
Which follows

Illegal instruction (reserved addressing fault) in . at 0x0 ($t1)
0x00000000 00000000 Invalid opcode.

I have urgent requirement of developing my application. Smilie
Any help is appreciated.

Thanks
-------------
Suman
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Programming

Shared library with acces to shared memory.

Hello. I am new to this forum and I would like to ask for advice about low level POSIX programming. I have to implement a POSIX compliant C shared library. A file will have some variables and the shared library will have some functions which need those variables. There is one special... (5 Replies)
Discussion started by: iamjag
5 Replies

2. 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

3. Red Hat

shared object

Hi, I would like to create a shared object ( .so). This shared object 1. uses the functions from a library. 2. Also it should be able to use the global variable in an app To achieve this what should I do ? 1) To use the functions in the library should I give the -ld option while... (1 Reply)
Discussion started by: rvan
1 Replies

4. HP-UX

Can't open shared library problem

I am getting following error when I am trying access PMCMD utility /usr/lib/dld.sl: Can't open shared library: /home/build3p/PMReleases/Zeus/HP-UX/xml/xerces2_4_0-icu2_6_1_811/lib/libxerces-c.sl.24 /usr/lib/dld.sl: No such file or directory Please help me with this (0 Replies)
Discussion started by: imran_affu
0 Replies

5. UNIX for Dummies Questions & Answers

Problem with shared dynamic library files

I am having a major problem. Most of the commands that i am running on my centos 5 system is giving the error of type: <dynamic shared library file>:open failed: No such file or directory For example: libgcc_s.so.1: open failed: No such file or directory How can i solve this? (6 Replies)
Discussion started by: proactiveaditya
6 Replies

6. UNIX for Dummies Questions & Answers

How to obtain list of object files in a shared (dynamic) library?

How can I simply obtain a list of the object files in a shared (dynamic) library. I am looking for the equivalent of "ar -t <lib>" for archived (static) libraries. Thanks in advance. :rolleyes: ---------- Post updated at 01:47 PM ---------- Previous update was at 12:16 PM ---------- The... (1 Reply)
Discussion started by: chatieremerrill
1 Replies

7. Shell Programming and Scripting

How to change a Makefile from building static library to shared library?

Hi: I have a library that it only offers Makefile for building static library. It built libxxx.a file. How do I in any way build a shared library? (either changin the Makefile or direct script or command to build shared library) Thanks. (1 Reply)
Discussion started by: cpthk
1 Replies

8. Programming

Shared library versioning problem at runtime

My executable was linked under RedHat using the LessTif GUI shared library. When I try to run it under UBUNTU, I get an error message that the LessTif library cannot be found. The LessTif library is there, but it is a newer VERSION. My executable is looking for the older version it was linked with.... (1 Reply)
Discussion started by: imagtek
1 Replies

9. Programming

Problem In Loading A Shared Object In Linux

Hi, We are trying to migrate our Solaris Soft OSE application to Linux. We use the dynamically linked options of the soft ose in our application. We are facing plenty of unresolved symbol problems while trying to load the ".so". These symbols are present in the libsoftose.a. for e.g ... (1 Reply)
Discussion started by: phani@tcs
1 Replies

10. HP-UX

Shared Library Problem

I have this error when I try to do check on the oracle database... Can you help me figure out whats the problem? Thanks for all the help! /usr/lib/pa20_64/dld.sl: Unable to find library 'libjox8.sl'. /usr/lib/pa20_64/dld.sl: Unable to find library 'libjox8.sl'. ... (1 Reply)
Discussion started by: vinz
1 Replies
Login or Register to Ask a Question
ldd_pa(1)						      General Commands Manual							 ldd_pa(1)

NAME
ldd_pa: ldd - list dynamic dependencies of executable files or shared libraries on PA-RISC systems SYNOPSIS
filename... Remarks This manpage describes on PA-RISC systems. For on Integrity systems, see ldd_ia(1). DESCRIPTION
is a command that can list the dynamic dependencies of incomplete executable files or shared libraries. lists verbose information about dynamic dependencies and symbol references. If the object file is an executable file, lists all shared libraries that would be loaded as a result of executing the file. If it is a shared library, lists all shared libraries that would be loaded as a result of loading the library. uses the same algorithm as the dynamic loader and to locate the shared libraries. See and sections in dld.sl(5) for more information. Options recognizes the following options: PA-RISC 32-bit only. Used in conjunction with and/or to force to bind all dependent libraries and report unsats. By default the smartbind mechanism in only binds libraries whose symbols are explicitly referenced. Check reference to data symbols. Check reference to data and code symbols. Display the search path used to locate the shared libraries. Display all dependency relationships. EXTERNAL INFLUENCES
Environment Variables uses the following environment variables to locate shared libraries. PA-RISC 64-bit mode: A colon-separated list of path names which defines the search path for shared libraries at runtime. See in dld.sl(5) for more information. A colon-separated or space-separated list of libraries which the dynamic loader implicitly loads first at runtime. See in dld.sl(5) for more information. A colon-separated list of path names which defines the search path for shared libraries at runtime. See and in dld.sl(5) for more information. The following internationalization variables affect the execution of Determines the locale category for native language, local customs and coded character set in the absence of and other environment variables. If is not specified or is set to the empty string, a default of (see lang(5)) is used instead of Determines the values for all locale categories and has precedence over and other environment variables. Determines the locale that should be used to affect the format and contents of diagnostic messages written to standard error. Determines the locale category for numeric formatting. Determines the locale category for character handling functions. Determines the location of message catalogs for the processing of If any internationalization variable contains an invalid setting, behaves as if all internationalization variables are set to See envi- ron(5). DIAGNOSTICS
prints the record of shared library path names to stdout. The optional list of symbol resolution problems are printed to stderr. returns zero when the operation is successful. A non-zero return code indicates that an error occurred. EXAMPLES
By default prints a simple dynamic path information. This consists of the dependencies recorded in the executable (or the shared library) followed by the physical location where these libraries are found. The option causes to print dependency relationship along with the dynamic path information. The option causes to analyze all symbol references and print information about unsatisfied code and data symbols. The option causes to print the dynamic search path lists used to load the libraries in the order that the path lists are referenced: WARNINGS
does not list shared libraries explicitly loaded using dlopen(3C) or shl_load(3X). FILES
output file 32-bit PA-RISC dynamic loader 64-bit PA-RISC dynamic loader 32-bit dummy executable loaded to check the dependencies of shared libraries. 64-bit dummy executable loaded to check the dependencies of shared libraries. message catalog SEE ALSO
System Tools ld(1) invoke the link editor Miscellaneous a.out(4) assembler, compiler, and linker output dld.sl(5) PA-RISC dynamic loader Texts and Tutorials