Subject: Re: port-sparc64/29824
To: Chuck Silvers <chuq@chuq.com>
From: Michael <macallan18@earthlink.net>
List: netbsd-bugs
Date: 05/01/2005 18:15:03
--Signature_Sun__1_May_2005_18_15_04_-0400_PVHkI+L.b2Clov9+
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hello,

> > 2.) The X11 server is stuck in "libpthread" also it is not linked
> > against that library which is *really* suspicious.
>=20
> this I have no explanation for.

A stray -pthread in my host.cf. I'm rebuilding without it now.
I don't quite see how this could trigger it though, when the Xserver
doesn't use any pthread functions - how could we end up in libpthread?

> so this is really 3 bugs:
>=20
> (1) Xserver manipulates signal state in a signal handler (common).
> (2) Xserver is somehow calling libpthread functions (common? sparc64?
>       unclear).
> (3) pthreads are still kinda broken on sparc64 (sparc64).

At least. The call stack looks a bit hosed to me, maybe it's a corrupted
function pointer again like in other parts of xsrc.
In these cases -fno-strict-aliasing cured the problem, but I had that in
host.cf too.

have fun
Michael

--Signature_Sun__1_May_2005_18_15_04_-0400_PVHkI+L.b2Clov9+
Content-Type: application/pgp-signature

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

iQEVAwUBQnVU6MpnzkX8Yg2nAQK0/Qf/UwpDAsqDSMJzAwFYrEFpuYcLSVq1Vgar
0L+h8KA+X/2qmAUu3itOx8OaTV7qVOXBSQD357GtoC+8t5bnoqqTA6NnPWhQ33Bm
UX6QhQmgEN3yyKeSWFyerVKrUtaWWcI016hlGpsWocqwaHRJqtrY/ADCGm4W5C7n
Hr74CwFsQU6+KzdExsPKGti7Al90xkf1hP4IJi0I7DK0sVypR65Fby1qwkQwG1K8
REmCYZOcjy4PmcJaVVoJ7GQp/GjmCurkEyXEWMEPYrbFYpyatscWhR8jCV7A3vJQ
Z88jo0ll/amHvJuhrGBBhTH37vbuWcx/DGLOTSQaNvo81XDA/Dyyiw==
=nUGL
-----END PGP SIGNATURE-----

--Signature_Sun__1_May_2005_18_15_04_-0400_PVHkI+L.b2Clov9+--