[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

how to implement a spy?

From: Andreas Jellinghaus
Subject: how to implement a spy?
Date: Thu, 08 Sep 2005 13:44:24 +0200
User-agent: KNode/0.8.2


I moved several projects from our own generic ld() stuf
to libtool, but one project has a problem: pkcs11-spy.
this project is a shared object / plugin, that itself
also loads a shared object / plugin. the idea is that
it sits between the application (e.g. mozilla) and the
real plugin (e.g. and protocols each
call and return. extremely helpful for debugging.

but now  it seems this doesn't work well with ltdl().
could it be that our spy could finds its own functions
and symbold instead of those in the plugin it loads?
both is pkcs#11 api - i.e. both the
and the plugin it loads have the same symbols in them.

can I somehow tell lt_* functions to give me the code
in the module I'm loading, and _not_ from symbols
within itself? Or if my idea what might be wrong isn't
right, any idea else where the problem could be
or how I can debug it?

I'm using plain lt_dlinit, lt_dlopen, lt_dlsym, lt_dlclose.
using the with dl() functions instead it works fine.
but since the software needs to work on win32 (native),
mac os X, solaris and linux at least I'd be happier with
using ltdl, if possible.

Thanks for your help.

Regards, Andreas

reply via email to

[Prev in Thread] Current Thread [Next in Thread]