Subject: Re: Is netbsd-3.0/ld.elf.so is thread safe ???
To: Nick Hudson <nick.hudson@dsl.pipex.com>
From: sushant mathur <sushant.iet@gmail.com>
List: netbsd-users
Date: 04/17/2006 18:32:07
------=_Part_43228_16915711.1145278927287
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
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 i=
n
netbsd-1.6 or not
On 4/13/06, Nick Hudson <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. M=
y
> > Application uses multile threads which uses dlopen with RTLD_LAZY .
> >
> > Is netbsd-3.0/ld.elf.so is thread safe ???
>
> No
>
> Nick
>
------=_Part_43228_16915711.1145278927287
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
<p>Hi Sorry for Delayed response as i was on leave<br>well I need to ask so=
me more query on this issue</p>
<p>1)Can You Tell whether dlopen/dlsym bindings are thread specific or proc=
ess<br>specific,Is there any specfication which clearly specifies this ???<=
/p>
<p>2)If i want to make netbsd3.0 thread safe then is it sufficient to make =
all<br>dlopen/dlsym thread safe by doing mutex locking and unlocking?</p>
<p>3>If i want to make lazy binding thread safe on uniprocessor system, =
then<br>the code executed during lazy binding has to be made thread safe us=
ing<br>mutex lock and unlock?</p>
<p>4) My Application is working Fine on i686 but on arm it's giving the<br>=
problem,<br>So is it a architecture issue?</p>
<p>4) This is guaranteed by having the binder not modify any internal data<=
/p>
<p>structures, only doing atomic updates to the PLTGOT at the end. (T=
his</p>
<p>was not the case in old versions of NetBSD.Whether this change is presen=
t in<br>netbsd-1.6 or not</p>
<p> </p><br><br>
<div><span class=3D"gmail_quote">On 4/13/06, <b class=3D"gmail_sendername">=
Nick Hudson</b> <<a href=3D"mailto:nick.hudson@dsl.pipex.com">nick.hudso=
n@dsl.pipex.com</a>> wrote:</span>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Wednesday 12 April 2006 15:10=
, sushant mathur wrote:<br>> hi all<br>><br>><br>> I am using=
=20
netbsd-3.0 for developing some multi threaded application. My<br>> Appli=
cation uses multile threads which uses dlopen with RTLD_LAZY .<br>><br>&=
gt; Is netbsd-3.0/ld.elf.so is thread safe ???<br><br>No<br><br>Nick<br>
</blockquote></div><br>
------=_Part_43228_16915711.1145278927287--