BTW - I'm not sure of the protocol - should this have been sent via the
development list or entered into bugzilla?
Regards,
Colin
Colin Burgess wrote:
We have an issue where a nonPIC binary that is
* calling a function in a shared object
* calling another function in a shared object,
We have an issue where a nonPIC binary that is
* calling a function in a shared object
* calling another function in a shared object, which references the address of
the first function, saving it as a function pointer.
* later, calling yet another function (in a shared object) which invokes the