Answered question
This question has been answered.
Unanswered question
This question has not been answered yet.
we have a customer situation, that when we ask them to setup this LD_PRELOAD and somehow, the program still fails in the shared object we wanted to avoid using the setting.
The question is, is there away to inspect the load sequence of an executable?
Thanks
George
This is the accepted answer.
This is the accepted answer.
LD_PRELOAD doesn't exist in AIX, what you probably want is LDR_PRELOAD or LDR_PRELOAD64.
No entirely sure what you mean by load sequence? Do you mean in what order shared objects are loaded in?
Look at "dump -H" to see in what loader domains the executable searches in. You may also want to look at "ldd" to see what the binary loads during execution, not sure if it's in the order from the output though.
This is the accepted answer.
This is the accepted answer.
- flodstrom
- 2013-07-28T01:12:40Z
LD_PRELOAD doesn't exist in AIX, what you probably want is LDR_PRELOAD or LDR_PRELOAD64.
No entirely sure what you mean by load sequence? Do you mean in what order shared objects are loaded in?
Look at "dump -H" to see in what loader domains the executable searches in. You may also want to look at "ldd" to see what the binary loads during execution, not sure if it's in the order from the output though.
I meant the order of a shared obj is loaded or the real issue is we have call to an API which happens provided by two shared library. We need to know exact which API is called in the core dump file... We can't check ldd because this is an after fact scenario.
