Re: Shared Object Problem
From: Colin Renouf (root_at_rs6000.RnREnterprise.dyndns.org)
Date: 02/25/05
- Next message: gprimerib: "Re: can't mksysb to my 8mm tape"
- Previous message: jthvedt_at_yahoo.com: "jumbo frames slowed Oracle/Tivoli backups"
- In reply to: richardselvan_at_hotmail.com: "Shared Object Problem"
- Next in thread: richardselvan_at_hotmail.com: "Re: Shared Object Problem"
- Reply: richardselvan_at_hotmail.com: "Re: Shared Object Problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 25 Feb 2005 17:01:37 GMT
There is a trick I have done on other platforms that may work the same...
If you know all of the external method names you can create a new DLL with
the same names and entry points as the other shared objects, with the same
external function names and entry points but no other code. You then
rename the originals and have the new stubs load the real functions if
they are called. It is some work, but is doable - bit probably not
supported. I used to do this on other platforms so I could do tracing....
Cheers
Colin
On Fri, 25 Feb 2005 richardselvan@hotmail.com wrote:
>
>
> Our (old) vendors had delivered a customised product which is deployed
> like this: (using a security analogy)
>
> There is one common dll (common.a). And, for every type of security
> interface, there is one dll (like this: rsa.a, ssl.a, hsm.a, this.a,
> etc., and there is also a default.a). There is a configuration ini
> file, wherein we specify which proptocol is used in the site.
> (protocol=rsa|ssl|hsm) or, if nothing is specified, default.a is
> assumed.
>
> we use only common.a and default.a and there is no way we would be
> using any other protocol. This means all those other dll's are of
> practically no use to us. But every time I use the common.a, all the
> other .a's are loaded as well.
>
> The dump output shows all those files are referred in common.a. Someone
> must have coded, something like the below in common.c
>
> switch (protocol):
> case rsa:
> call_encrypt_in_rsa () ; break ;
> case hsm:
> call_encrypt_in_hsm () ; break ;
> .......
> case default:
> call_encrypt_in_dafault () ;
>
> etc.
>
> The problem is that, every time we use common.a/default.a all those
> sundry dll's are loaded as well, sitting there hogging memory... How do
> we prevent them from loading at all ?
>
> Is there anyway we can tell AIX not to bother loading them ? is there
> any tool using which we can edit the common.a binary to mark all those
> functions as unresolved ?
>
> (we can't go back to the vendors, they have gone since long)....
>
>
Colin Renouf
"AIX is user friendly. It's just choosy who its friends are."
- Next message: gprimerib: "Re: can't mksysb to my 8mm tape"
- Previous message: jthvedt_at_yahoo.com: "jumbo frames slowed Oracle/Tivoli backups"
- In reply to: richardselvan_at_hotmail.com: "Shared Object Problem"
- Next in thread: richardselvan_at_hotmail.com: "Re: Shared Object Problem"
- Reply: richardselvan_at_hotmail.com: "Re: Shared Object Problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
