--Signature_Tue__7_Jun_2005_07_34_40_-0400_niIDFNJecTYgb256
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hello,

>  So, should I open a PR with those infos ? As I understood the PR
>  (pointer by timo), it's not the same thing (as the later seems to
> deal with db4 compilation), right ?

Well, we can't really tell since the stack it thrashed. I guess you ran
the whole thing with debug-enabled binaries ( compiled with -g ) ?
libpthread is a system library so it won't get debug information from
that.

> > > don't know what all this means (expect my LDAP don't work :)
> > > tomorrow, I'll try to compile OpenLDAP with correct debugging info
> > > and redo the test.
> >=20
> > This means the crash happens in libpthread ( which is known to have
> > issues on sparc64 ) and something mucked up the stack. Sorry, it
> > doesn't seem to be something obvious and trivial :/

>  erf... so I'll try to use mysql till it works (or maybe openldap with
>  some - solaris/sparc64, openbsd/sparc64, netbsd/sparc - emulation)

I guess that's the way to go.

goos luck
Michael

--Signature_Tue__7_Jun_2005_07_34_40_-0400_niIDFNJecTYgb256
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (NetBSD)

iQEVAwUBQqWGUcpnzkX8Yg2nAQJKJgf/cMr+Y1vxAt1vfHrba8c8hDtGOgcSl8vf
G3J2t5EJxs5xWR+e53HVn7A/VeYt4hPqhaynaEnUmQP1Bev1IS9pRCkZecvs2lEb
QykXKn4wwXs2SMDl6no5YoyV34m2cSmibFTPZ4ySi0tq4Ji5QUYSwD7ofLRlsgHN
yV5dGX716at0CWhRodbX8IGcPL4hcGckkzqtIY7zAT2fprX1APrSEVHg4HRtbYNS
PN7outI1GQL9yW8Jd84NAAgOozNNR6VIkT7zcJ64u+QdJTmAABAUSkMHE5z7AIIF
a+DQCF6gIzIaTku4Xo5Wt0Gm0+CRzm5MROEI0m4fyN+IG7j4mD3bSw==
=Gh0e
-----END PGP SIGNATURE-----

--Signature_Tue__7_Jun_2005_07_34_40_-0400_niIDFNJecTYgb256--