Date: Wed, 25 Feb 2004 13:19:06 +0100 From: Adriaan de Groot <adridg@cs.kun.nl> To: freebsd-amd64@freebsd.org Subject: Re: The return of threading errors in ogg123 Message-ID: <200402251319.11569.adridg@cs.kun.nl> In-Reply-To: <200402250301.i1P31COh071628@bigtex.jrv.org> References: <Pine.GSO.4.44.0402171025520.15647-100000@wn4.sci.kun.nl> <200402242111.39048.adridg@cs.kun.nl> <200402250301.i1P31COh071628@bigtex.jrv.org>
next in thread | previous in thread | raw e-mail | index | archive | help
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 25 February 2004 04:01, James Van Artsdalen wrote: > > From: Adriaan de Groot <adridg@cs.kun.nl> > > Date: Tue, 24 Feb 2004 21:11:33 +0100 > > > > looks like the stack-16-alignment has gotten broken again somewhere. > > Hack the gcc function epilogue code to test %rsp before each return and > branch to abort if stack is mis-aligned, or, maybe load 8(%rsp) to %xmm7 = or > something like that to force a fault. That will get you close to the sce= ne > of the crime, and flush out others that aren't near FP code. Ummm ... "Dammit Jim, I'm a doctor of computer science, not a compiler=20 hacker!" Can you give a suggestion? Although I'm not averse to wasting my=20 time figuring out how to do all those things, I think I'd rather waste it b= y=20 fixing the ed(4) driver. =2D --=20 pub 1024D/FEA2A3FE 2002-06-18 Adriaan de Groot <groot@kde.org> Would you like a freem? =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAPJK/dqzuAf6io/4RAjZPAJ9ZA34W9FRRRVaLjO+6Z031xFpicQCfXm4d N13I5qby0X/cf4EDU67ulhs=3D =3Dsckq =2D----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200402251319.11569.adridg>