Solaris fcntl CPU/Lock update

[Esh, Andrew]

gdb is thread aware. "help running" shows thread commands.

Note that gdb does not report the libraries it loads to support itself. The
ones listed are being searched for symbols to support the program being
debugged. If the thread library is being searched, it is because the program
being debugged requires it, or one of the libraries required by the program
requires it.

My guess is that one of the libraries listed above libpthread in the debug
output requires pthreads. Probably LDAP, since it is listed just prior.
libmp is interesting too. Multi-processor?


> -----Original Message-----
> From: Pierre Belanger [mailto:pbelang1 at oss.cantel.rogers.com]
> Sent: Tuesday, February 04, 2003 5:16 PM
> To: David Collier-Brown -- Customer Engineering
> Cc: samba-technical at samba.org; Christopher R. Hertel
> Subject: Re: Solaris fcntl CPU/Lock update
> 
> 
> Hello,
> 
> David Collier-Brown -- Customer Engineering wrote:
> > "Christopher R. Hertel" wrote: indirectly to you from pbelanger:
> > 
> Thanx Christopher to forward the info.
> 
> 
> >><pbelanger> Please let know jra that libnspr4.so and 
> libnss3.so ARE linked
> >>            to libpthread and libthread under Solaris
> >
> > 	I assume libnspr4.so and libnss3.so are special libraries
> > 	provided as part of open LDAP: the Solaris nss libraries are
> > nss_compat.so.1   nss_files.so.1    nss_nis.so.1      nss_user.so.1
> > nss_dns.so.1      nss_ldap.so.1     nss_nisplus.so.1  nss_xfn.so.1
> > 	with nothing resembling libnss3, while there are no
> > 	nspr libraries at all.
> > 
> > 	I did a quick check, and there are no solaris libraries
> > 	which make calls into libposix...
> >
> I would suggest to compile Samba using OpenLDAP instead of
> Sun's (Netscape) LDAP libraries and see if there's still
> a problem.
> 
> The back-trace looks *very* weird. gdb is not "thread aware"
> as far as I remember? Could it be the reason why the
> back-trace is "weird"?
> 
> I'd seriously think of compiling using OpenLDAP, I'd like to
> see the results. I'm even thinking of download Sun's SDK and
> play around with it to see if I get the same problem here,
> but I'm way too busy for the next few days.
> 
> Cheers,
> Pierre B.
> 
>