Re: dlopen() functions calling symbols in parent

2006-11-30 Thread Ian Lindsay
> but the point can be made to the authors. -E exports *all* non-static > symbols, which will allow loadable modules to gain easy access to symbols > they are not supposed to. perhaps a more elegant solution: http://gcc.gnu.org/wiki/Visibility

Re: dlopen() functions calling symbols in parent

2006-11-29 Thread Pawel S. Veselov
On Wed, Nov 29, 2006 at 11:28:25PM +, Brian Candler wrote: >On Wed, Nov 29, 2006 at 09:16:54AM -0800, Pawel S. Veselov wrote: >> the better way to do this is to put 'bar()' in another shared object, and >> dlopen() it before the "module" with the RT_GLOBAL flag. >> I put the modified stuff in h

Re: dlopen() functions calling symbols in parent

2006-11-29 Thread Brian Candler
On Wed, Nov 29, 2006 at 09:16:54AM -0800, Pawel S. Veselov wrote: > the better way to do this is to put 'bar()' in another shared object, and > dlopen() it before the "module" with the RT_GLOBAL flag. > > I put the modified stuff in http://manticore.2y.net/temp/callbacks Thank you - although that

Re: dlopen() functions calling symbols in parent

2006-11-29 Thread Pawel S. Veselov
the better way to do this is to put 'bar()' in another shared object, and dlopen() it before the "module" with the RT_GLOBAL flag. I put the modified stuff in http://manticore.2y.net/temp/callbacks thanks, Pawel. On Wed, Nov 29, 2006 at 10:36:20AM -0600, Dale Rahn wrote: >Hmm, it seems that -rdy

Re: dlopen() functions calling symbols in parent

2006-11-29 Thread Dale Rahn
Hmm, it seems that -rdynamic is a non-standard flag here. Use '-Wl,-E' or '-Wl,--export-dynamic'. Check the ld(1) man page for '-E' and '--export-dynamic' options. http://www.cim.mcgill.ca/~franco/OpSys-304-427/messages/node59.html On Wed, Nov 29, 2006 at 03:52:37PM +, Brian Candler wrote: >