Date: Thu, 30 Oct 2003 23:04:16 -0800 From: Kris Kennaway <kris@obsecurity.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: kris@obsecurity.org Subject: Re: __fpclassifyd problem Message-ID: <20031031070416.GA35316@rot13.obsecurity.org> In-Reply-To: <20031030.234813.72025638.imp@bsdimp.com> References: <20031029211951.GA12398@rot13.obsecurity.org> <20031029152202.C7702@pooker.samsco.home> <20031029154141.T7702@pooker.samsco.home> <20031030.234813.72025638.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 30, 2003 at 11:48:13PM -0700, M. Warner Losh wrote: > In message: <20031029154141.T7702@pooker.samsco.home> > Scott Long <scottl@freebsd.org> writes: > : To respond to myself, I got ahold of a 4.8 libm.so and made sure that t= he > : linker used it. No change in the problem, and it still hints that the > : native libc is being linked in. >=20 > You might want to enable debugging of ld.so to confirm. This was understood already (java is doing a dlopen of /usr/lib/libc.so). Kris --0OAP2g/MAC+5xKAE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/oglwWry0BWjoQKURAiXTAJ9pJmv0plPRe0hP/0AYViuMkkIs2QCg3AzR QcMCLGBSJFc0WA1U1qXzJr4= =I4eO -----END PGP SIGNATURE----- --0OAP2g/MAC+5xKAE--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031031070416.GA35316>