Hi Sorry for Delayed response as i was on leave well I need to ask some more query on this issue
1)Can You Tell whether dlopen/dlsym bindings are thread specific or process specific,Is there any specfication which clearly specifies this ???
2)If i want to make netbsd3.0 thread safe then is it sufficient to make all dlopen/dlsym thread safe by doing mutex locking and unlocking?
3>If i want to make lazy binding thread safe on uniprocessor system, then the code executed during lazy binding has to be made thread safe using mutex lock and unlock?
4) My Application is working Fine on i686 but on arm it's giving the problem, So is it a architecture issue?
4) This is guaranteed by having the binder not modify any internal data
structures, only doing atomic updates to the PLTGOT at the end. (This
was not the case in old versions of NetBSD.Whether this change is present in netbsd-1.6 or not
On 4/13/06, Nick Hudson <dsl.pipex.com">nick.hudson dsl.pipex.com> wrote:
On Wednesday 12 April 2006 15:10, sushant mathur wrote: > hi all > > > I am using
netbsd-3.0 for developing some multi threaded application. My > Application uses multile threads which uses dlopen with RTLD_LAZY . > > Is netbsd-3.0/ld.elf.so is thread safe ???
No
Nick
|